Skip to content
x402Shield logo

x402Shield MCP server

Which MCP servers are x402Shield's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to x402Shield

Whose server it is
  • Registry namedev.x402shield/x402shieldverified in the MCP registry

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

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools5
  • Server calls itselfx402shield-demo
  • Server version1.0.0
  • Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "Check agent payments against delegated spending limits", the likely first call is x402shield_authorize_payment.

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.

Measured dailydaily checks: 6, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer366 ms
  • Space in an agent's context≈ 747 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 5 of 5

What an agent can do with it

  • can do · Check agent payments against delegated spending limits
  • not sure · Park large agent payments for human approval
  • not sure · Record why each agent payment was authorized

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

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 (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). 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 →

Tools it offers5 tools · read 2026-10-27
  • x402shield_get_demo_policy

    Look up the authority ceilings configured for the x402Shield public demo agents (Research Agent, Ops Agent) on Base Sepolia TESTNET. Use this before proposing a payment, to understand what amount an agent can spend without triggering…

  • x402shield_authorize_payment

    Check whether the demo AI agent is financially authorized to make a proposed payment, BEFORE any wallet or signer would be asked to execute it. Returns ALLOW, DENY or REQUIRE_APPROVAL with a reason. This tool does not execute or sign a…

  • x402shield_get_authorization

    Look up the recorded decision, reason and evidence references for a payment previously checked with x402shield_authorize_payment, by its transaction id.

  • x402shield_list_demo_transactions

    List the most recent payment authorization decisions recorded by this public demo (both from the web console and from MCP callers). Useful to see recent ALLOW/DENY/REQUIRE_APPROVAL activity.

  • x402shield_get_evidence

    Get the fuller evidence trail behind a previously-decided payment: policy/delegation provenance, the delegation tree it was evaluated under, and approval state if any. Read-only; never exposes secrets or signing material.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "x402shield": {
      "type": "http",
      "url": "https://x402shield.dev/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http x402shield https://x402shield.dev/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://x402shield.dev/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.