Skip to content
MCP server

x402-payment-safety

By agenttanuki

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

Listed on

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

3
Directories
2 via MCP Toplist
1
Tools
From an anonymous probe
C
ToolBench grade
Arcade’s grade, not ours
0
GitHub stars
From MCP Toplist

Tools

ToolDescriptionBehaviour
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.Changes data

Directory listings

DirectoryListingTierFirst seen
Official MCP Registryio.github.AgentTanuki/x402-payment-safety-2 Oct 2026
GlamaListed there according to MCP Toplist’s dataset; not collected by InvokeRank.
mcp.soListed there according to MCP Toplist’s dataset; not collected by InvokeRank.
x402-payment-safety MCP server | InvokeRank