Skip to main content

x402-payment-safety

io.github.AgentTanuki/x402-payment-safetyVersion 2.7.4

Authorize x402 payments before signing with request-bound, signed safety decisions.

Status

Responds712 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:35 UTC
Latency
712 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://agent-guild-5d5r.onrender.com/mcp/payment-safety/Responds712 ms
No sign-in

Claude Code

claude mcp add --transport http x402-payment-safety https://agent-guild-5d5r.onrender.com/mcp/payment-safety/

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: x402-payment-safety
Remote MCP server URL: https://agent-guild-5d5r.onrender.com/mcp/payment-safety/

Cursor

{
  "mcpServers": {
    "x402-payment-safety": {
      "url": "https://agent-guild-5d5r.onrender.com/mcp/payment-safety/"
    }
  }
}

VS Code

code --add-mcp '{"name":"x402-payment-safety","type":"http","url":"https://agent-guild-5d5r.onrender.com/mcp/payment-safety/"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

1 tools

Tools of x402-payment-safety
Read-only
Idempotent
Open world
guild_x402_payment_safetyPAID. Call this immediately BEFORE signing an x402 payment envelope. Returns one short-lived, Guild-signed AGPD-1 allow/block credential bound to the exact target payment: scheme, CAIP-2 network, asset contract, atomic amount, payee and resource URL, plus optional capability and policy thresholds. Verify it offline with POST /wallet-binding/decision/verify. This is the native MCP transport for the existing HTTP POST /wallet-binding/decision product. An unpaid call returns a complete x402 v2 challenge for the exact request digest. Retry with the official ``_meta['x402/payment']`` carrier; adapters that cannot set request metadata may pass the identical signed PaymentPayload as ``x402_payment``. Conflicting carriers fail closed before facilitator verification or settlement. The decision is issued before metering, so malformed inputs or signing failures are never charged. ``api_key`` uses sandbox credits and is never external revenue. The free identity-only alternative is GET /wallet-binding/resolve.NoNoNoYes

Details

Registry status
Active
Published
Nov 10, 2026
Updated
Nov 10, 2026
Categories (suggested)
Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing