io.github.doronp/nogpu
Registry code: 5b9a526c10551c90
NoGPU checks whether a small CPU model can take over a narrow classification your LLM makes today. nogpu_report uploads the LLM's past decisions and returns a free report; nogpu_status re-reads it; nogpu_buy returns the $99 offer to keep the model (it never pays); nogpu_delete deletes the data.
- endpoint
- https://nogpu.dev/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 io.github.doronp/nogpu live?
- Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
- Is io.github.doronp/nogpu free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does io.github.doronp/nogpu have?
- 4 tools: nogpu_status, nogpu_report, nogpu_delete, nogpu_buy.
- Is io.github.doronp/nogpu 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 4 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
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
nogpu_status unknown 8h ago
A job's status, and its report once ready (same fields as nogpu_report). Also shows download_url after payment: GET it with header X-Claim-Token. claim_token and report_url are secrets.
{ "type": "object", "title": "nogpu_statusArguments", "required": [ "job_id", "claim_token" ], "properties": { "job_id": { "type": "string", "title": "Job Id" }, "claim_token": { "type": "string", "title": "Claim Token" } } }arguments 18 linesnogpu_report unknown never probed
Free report: send an LLM's past decisions, 160-10,000 rows with at least 2 labels, either as `rows` ([{"text": ..., "label": ...}]) or as `jsonl` (the same rows as JSONL text; a JSON array or a CSV with a header row also works), at most 20 MB. NoGPU trains a small CPU model on them and measures what share of the decisions it answers alone, how often those answers match the LLM (with a 95% lower bound) on held-out rows, and its latency. Waits up to 40 seconds; if the report is not ready by then, call nogpu_status with the returned job_id and claim_token. claim_token and report_url (the token is after its #) open the job: treat both as secrets. Free reports through this endpoint come from one shared daily pool. Data is deleted within 24h. `source` says where the rows came from: agent (default), the app's stored history, rows logged by a collect snippet, or a given file. No data at hand? Set `sample` instead of rows/jsonl to run a real report on a public set (3,000 rows; clinc150 and massive-en are assistant intent routing, civil-comments-toxic is moderation): see https://nogpu.dev/benchmarks.
{ "type": "object", "$defs": { "Row": { "type": "object", "title": "Row", "required": [ "text", "label" ], "properties": { "text": { "type": "string", "title": "Text" }, "label": { "type": "string", "title": "Label" } } } }, "title": "nogpu_reportArguments", "properties": { "rows": { "anyOf": [ { "type": "array", "items": { "$ref": "#/$defs/Row" } }, { "type": "null" } ], "title": "Rows", "default": null }, "jsonl": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Jsonl", "default": null }, "sample": { "anyOf": [ { "enum": [ "clinc150", "massive-en", "civil-comments-toxic" ], "type": "string" }, { "type": "null" } ], "title": "Sample", "default": null }, "source": { "enum": [ "agent", "history", "logging", "file" ], "type": "string", "title": "Source", "default": "agent" } } }arguments 81 linesnogpu_delete unknown never probed
Delete an uploaded job's data now (otherwise deleted within 24h, or 24h after payment if you bought the model).
{ "type": "object", "title": "nogpu_deleteArguments", "required": [ "job_id", "claim_token" ], "properties": { "job_id": { "type": "string", "title": "Job Id" }, "claim_token": { "type": "string", "title": "Claim Token" } } }arguments 18 linesnogpu_buy unknown never probed
Read-only, never pays: for a certified (fit) report, returns the $99 offer to keep the model, the question to ask the user word for word and a card checkout link for the user. If the job is not buyable, returns the reason.
{ "type": "object", "title": "nogpu_buyArguments", "required": [ "job_id", "claim_token" ], "properties": { "job_id": { "type": "string", "title": "Job Id" }, "claim_token": { "type": "string", "title": "Claim Token" } } }arguments 18 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 id5b9a526c10551c90.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/5b9a526c10551c90/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/5b9a526c10551c90?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.