computescreener
Registry code: d91c4796deda6d0f
Compute Screener publishes two daily price indices. GPU prices are collected every 2 to 3 hours; token prices once a day. GPU rental: USD per GPU-hour for H100, H200, A100, B200, B300, MI300X, RTX PRO 6000, each standardized to an on-demand, 8-GPU, US contract; one value per day in US Central time, the current day provisional. AI tokens: USD per 1M tokens (3 input : 1 output blend) for Anthropic, OpenAI, Google, xAI, Meta, Moonshot AI, Alibaba, DeepSeek, Z.ai, Xiaomi, one value per UTC day. Changes (change_1d_pct, change_1w_pct, change_1m_pct) are percent changes from the value that many days…
- endpoint
- https://computescreener.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is computescreener live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is computescreener free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does computescreener have?
- 3 tools: get_price_history, get_gpu_prices, get_token_prices.
- Is computescreener safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_gpu_prices open 1h ago
Latest GPU rental price index in USD per GPU-hour, with 1D, 1W and 1M changes and a link to each GPU's page. Give one GPU to also get its benchmark contract, each provider's standardized average price, and the exchanges listing a contract on its rental price: each exchange's last price and 24-hour volume, read from its public market-data API within the last minute.
{ "type": "object", "properties": { "gpu": { "enum": [ "H100", "H200", "A100", "B200", "B300", "MI300X", "RTX PRO 6000" ], "type": "string", "description": "One GPU; omit for all listed GPUs." } }, "additionalProperties": false }arguments 19 linesget_token_prices open 1h ago
Latest token price index per AI company in USD per 1M tokens (3 input : 1 output blend), with 1D, 1W and 1M changes. Give one company to also get its models' usage shares and posted prices.
{ "type": "object", "properties": { "company": { "enum": [ "Anthropic", "OpenAI", "Google", "xAI", "Meta", "Moonshot AI", "Alibaba", "DeepSeek", "Z.ai", "Xiaomi" ], "type": "string", "description": "One company; omit for all listed companies." } }, "additionalProperties": false }arguments 22 linesget_price_history unknown 1h ago
Price history of one GPU (USD per GPU-hour) or one AI company (USD per 1M tokens), oldest first. GPU history is daily from 2025-11-07 for H100 and A100 and from 2026-10-23 for the others, weekly before; token history is daily from 2025-01-01.
{ "type": "object", "required": [ "name" ], "properties": { "days": { "type": "integer", "default": 30, "maximum": 1000, "minimum": 1, "description": "How many days back from the latest value." }, "name": { "enum": [ "H100", "H200", "A100", "B200", "B300", "MI300X", "RTX PRO 6000", "Anthropic", "OpenAI", "Google", "xAI", "Meta", "Moonshot AI", "Alibaba", "DeepSeek", "Z.ai", "Xiaomi" ], "type": "string", "description": "A GPU or an AI company." } }, "additionalProperties": false }arguments 39 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idd91c4796deda6d0f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d91c4796deda6d0f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d91c4796deda6d0f?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.