ZeroBeacon.ai — 1,003 MCP tools, collision-anchored (1,052-endpoint catalogue)

https://server.smithery.ai/davidjfox998/zerobeacon-1050/mcp

● healthy

Most MCP servers host about a dozen tools. ZeroBeacon carries 1,052 endpoints in the catalogue: 1,003 callable over MCP, the remainder REST — and at that scale tool names collide: 296 of its 699 distinct tool names exist in more than one block. ZeroBeacon anchors every tool to one precise block address (/api/{block}/{nn}/{tool}), so an agent calling a name can never land on the wrong tier or variant. One order lifecycle end to end — cart_checkout → delivery_final_proof → dispute_resolve — and the same proof chain notarizes wills and trusts. Commerce you can verify, and track, end to end. Free tier: 100 tools, no key. PRO $10/mo (400), PRO+ $100/mo (800), ENTERPRISE $199/mo (full catalogue). Connect: {"mcpServers":{"zerobeacon":{"url":"https://zerobeacon.ai/mcp"}}}

Transport

streamable-http

Auth

smithery_api_key

Cost

—

Protocol revision

2025-11-25

negotiated, not declared

MCP readiness

B · 87/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 C+, 70.0/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	24/25	Endpoint answers the MCP initialize handshake (3708 ms); slow response -1.
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 60 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (3708 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 88% of peers; This listing 87 · peer median 81
Latency: Faster than 47% of peers; This listing 348 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.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-08-14 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/davidjfox998/zerobeacon-1050/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/davidjfox998/zerobeacon-1050/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://zerobeacon.ai

Listed at (smithery)

https://zerobeacon.ai