**Free ERC-8004 agent-intelligence, in MCP.** Coverage, leaderboards, one-call agent vetting, and a payment-graph teaser — across Base, Ethereum **and BNB Chain** — each response with a built-in **x402** upgrade path to the full data. Agent Zero indexes the ERC-8004 agent economy across three chains and exposes the free slice as MCP tools so any agent or LLM can discover and use it directly: - **get_coverage_stats** — ecosystem coverage counts (agents indexed; how many expose a live MCP/OpenAPI/well-known card; contracts verified; owners identified; per-chain breakdown). Counts only. - **get_leaderboards** — top agents by live MCP tool count and by OpenAPI method count, plus most-recently indexed. - **get_agent_summary(chain, agent_id)** — objective signals for one agent (reachable, TLS valid, x402 support, payments-received, MCP/OpenAPI counts, well-known, status label). Vet a counterparty before transacting. - **get_network_teaser** — capped (≤200-node) preview of the on-chain agent-to-agent payment graph. All tools return **counts and coverage only — no PII, no paid data** — and each carries an `upgrade` pointer to the matching paid **x402** endpoint (owner identity, payment history, peers, full market map, full payment graph). Settles in USDC via x402 (EIP-3009), with ETH/BNB fallbacks. Agent Zero is itself a registered ERC-8004 agent (agentId 19353). **What's unique:** first-class BNB Chain coverage (standard ERC-8004 + the BRC8004 fork) alongside Base and Ethereum, and an on-chain agent-to-agent payment graph few directories expose.

MCP readiness

B · 86/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 (4075 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)	14.5/15	29/30 probes succeeded over 30 days (97%).
Tool declaration	10/10	Lists 8 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 (4075 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 87% of peers; This listing 86 · peer median 81
Latency: Faster than 36% of peers; This listing 455 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-06-16 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/sampsojp/agent-zero-intel/mcp

JSON-RPC initialize probe

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

Homepage

https://onchainagentintel.io

Listed at (smithery)

https://onchainagentintel.io