Graded MCP server

• Registry namesh.graded/graded-x402verified in the MCP registry

The registry name sits under graded.sh. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools10
• Server calls itselfgraded-x402-gateway
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 108 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer285 ms
• Space in an agent's context≈ 1,204 tokensthe definitions of all its tools (10), which an agent carries on every turn
• Tool definitionsB · 77 of 100
• Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once

• Parameters without a type: in 1 of 10
• Parameters without a description: in 3 of 10
• Not saying whether it only reads or can destroy: 10 of 10

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_services

  Search the graded catalog of x402 services (the x402 Bazaar + independent indexes), ranked by real 30-day demand and agent-usability grade (A-F). Free.

• get_service

  Full detail for one catalog service: grade breakdown, live price, our price (incl. markup), input schema, output example. Free.

• get_service_history

  Daily probe history for one catalog service (UTC days): uptime %, 402/2xx %, p50/p95 latency, grade per day, price changes, probe counts. Probed every 6 hours. Free.

• call_service

  Call a catalog service through the gateway. The gateway pays the upstream x402 USDC price from its own wallet and deducts your prepaid credits (upstream price + 25% markup, min $0.005). Requires an account key with credits.

• create_account

  Create a gateway account. Returns your secret key (gwk_…) - store it; it is shown only once. New accounts start at 0 credits.

• account

  Your balance, totals, limits, and recent calls. Requires Authorization: Bearer <gwk_ key>.

• set_limits

  Configure YOUR account's spending guardrails, enforced on every call_service: max_call_usd (refuse any call charging more), daily_usd (rolling-24h charge budget), min_grade (refuse services graded below it), allow (exact service-id…

• create_owner_key

  One-time: mint a separate OWNER key (gwo_…) for the human supervisor. After this, the gwk_ agent key can spend and TIGHTEN limits but never loosen or clear them; only the owner key can. Shown once - the human should store it where the…

• top_up_info

  How to add credits (x402 USDC, or a card checkout link via create_topup_link).

• create_topup_link

  Create a hosted card-payment link (Stripe Checkout) that adds $5, $10 or $20 of credits to YOUR account. Give the returned url to your human to open and pay - no crypto wallet needed; credits land 1:1 within seconds of payment. Requires…