Is the Graded X402 MCP server down?

mcp-registry/sh.graded/graded-x402 · v1.0.0

healthy
Last checked 2026-10-25 12:16 UTC · handshake 333ms

As of 2026-10-25 12:16 UTC, the Graded X402 MCP server is up with a Glimind reliability score of 67/100 (grade C). Over the last 30 days it answered 98.2% of Glimind's liveness checks. It had 95 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
98.2%
checks observed
4,757
outages (90d)
95
tools
10

Discover and call 2,000+ x402 machine-payable services through one graded API key + gateway.

Install Graded X402 MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http graded-x402-mcp-server https://graded.sh/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "graded-x402-mcp-server": {
      "type": "http",
      "url": "https://graded.sh/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (70/100)

C (70/100): 0 error(s), 5 warning(s) across 10 tool(s); ~1,336 tokens of tool definitions.
Scores higher than 4% of 15,680 MCP servers Glimind has audited.
Its tool list costs an agent ~1,336 tokens per session — lighter than 65% of servers.
68 → 70 since 2026-10-17
no tool-poisoning patterns
Schemas85
Descriptions69
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability75
Stability100

What to fix (6)

10 of 10 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: account, call_service, create_account, create_owner_key, create_topup_link and 5 more

4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_account, create_owner_key, create_topup_link, set_limits

3 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: call_service, get_service, get_service_history

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: call_service

Reachable 98.2% of the time over the last 30 days; median recovery 7 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 9 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fsh.graded%2Fgraded-x402/fixes

call_service 1 change
{
  "name": "call_service",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string"
      },
      "body": {
        "description": "JSON body for POST services",
        "type": "string"
      },
      "query": {
        "type": "object",
        "description": "URL query params",
        "additionalProperties": {}
      }
    },
    "additionalProperties": false
  }
}
create_account 1 change
{
  "name": "create_account",
  "description": "Create a gateway account. Returns your secret key (gwk_…) - store it; it is shown only once. New accounts start at 0 credits.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
create_owner_key 1 change
{
  "name": "create_owner_key",
  "description": "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 agent can't read it. Requires Authorization: Bearer <gwk_ key>.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/sh.graded/graded-x402"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/sh.graded/graded-x402"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fsh.graded%2Fgraded-x402.svg)](https://glimind.com/server/mcp-registry%2Fsh.graded%2Fgraded-x402?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fsh.graded%2Fgraded-x402?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fsh.graded%2Fgraded-x402.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fsh.graded%2Fgraded-x402.svg
   :target: https://glimind.com/server/mcp-registry%2Fsh.graded%2Fgraded-x402?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c476141152ce1b50…, first seen 2026-10-17, included at leaf 9266 of 65,982. Version history · verify what your client received.

Tools (10)

Compare: most reliable finance servers · most reliable other servers · most reliable security servers · most reliable payments servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Graded X402 MCP server down right now?

As of 2026-10-25 12:16 UTC, the Graded X402 MCP server is up with a Glimind reliability score of 67/100 (grade C). Over the last 30 days it answered 98.2% of Glimind's liveness checks. It had 95 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Graded X402 MCP server provide?

Graded X402 MCP server advertises 10 tools, including account, call_service, create_account, create_owner_key, create_topup_link.

How do I install Graded X402 MCP server?

Point your MCP client at this streamable-http endpoint: https://graded.sh/mcp

Is the Graded X402 MCP server safe to connect to an AI agent?

Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Graded X402 MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve