x402 agent safety MCP

https://x402-safety-mcp.dgdb.workers.dev/mcp

● healthy

Paid MCP tools for AI agents on Base. Pre-transaction safety: decode what you're signing (EIP-712/Permit/calldata), detect address-poisoning look-alike recipients, audit dangerous approvals, check recipients against a live on-chain malicious-address DB, or run every check in one call. Live infrastructure feeds: which Base public RPCs are serving a stale chain tip (parallel-probed every 30s), which x402 endpoints are up or broken, ecosystem map, market churn and catalog diffs. Deterministic, no LLM, evidence-backed. $0.005-$0.02 per call in USDC via x402.

Transport

streamable-http

Auth

—

Cost

—

Protocol revision

2025-11-25

negotiated, not declared

MCP readiness

B · 81/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 82.5/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (926 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 19 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	0/5	not seen in a source for over 30 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (926 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 52% of peers; This listing 81 · peer median 81
Latency: Faster than 17% of peers; This listing 697 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

submission since 2026-06-28 ↗

How to connect

MCP endpoint (streamable-http)

https://x402-safety-mcp.dgdb.workers.dev/mcp

JSON-RPC initialize probe

curl -X POST https://x402-safety-mcp.dgdb.workers.dev/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://x402-safety-mcp.dgdb.workers.dev/mcp

Listed at (submission)

https://x402-safety-mcp.dgdb.workers.dev/mcp