What we measured

Over the last 30 days we probed this MCP server 7 times on 7 days; it answered 7 (100%). Median response 103 ms, 95th percentile 130 ms.

When we called tools/list it returned 2 tools, including approvals_quote, approvals_check_address, over MCP protocol revision 2026-07-28.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 88% and higher on readiness than 55%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

Tools (2)

As returned by the server's own tools/list when we called it.

approvals_quote: Free: price, payTo and the exact x402 URL to buy a Base ERC-20 approval risk report (unlimited/over-balance approvals + revoke calldata) for a wallet.
approvals_check_address: Free: checks the 0x address format and whether it is an EOA or contract on Base before you pay.

MCP readiness

B · 82/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B+, 94.8/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 (130 ms).
Protocol revision	10/10	Speaks the current MCP revision 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	7/7 probes succeeded over 30 days (100%).
Tool declaration	5/10	Lists 2 tool(s) with descriptions.
Verified identity	7/10	Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags	2/5	seen within 30 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

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

Measured 2026-11-12.

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,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness: Higher than 55% of peers; This listing 82 · peer median 81
Latency: Faster than 88% of peers; This listing 112 ms · peer median 349 ms

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

Tool declaration −5 — Declare every tool with a description and input schema.
Now: Lists 2 tool(s) with descriptions.
Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
Verified identity −3 — Claim the listing and prove control of its domain.
Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

submission since 2026-11-06 ↗ mcp-registry since 2026-11-06

How to connect

MCP endpoint (streamable-http)

https://approvals.madebydevx.com/mcp

JSON-RPC initialize probe

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

Homepage

https://approvals.madebydevx.com/mcp

Listed at (submission)

https://approvals.madebydevx.com/mcp