mcp server
Agent Zero — ERC-8004 Agent Intelligence
Free read-only ERC-8004 agent-intel tools: coverage, leaderboards, agent vetting, payment graph
Description as published by the maintainer. Source
- version 1.8.0
- active
- retrieval
active — Registry entry last updated 2026-06-15. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_agent_summary(chain, agent_id)- Objective, counts-only signals for one ERC-8004 agent. Args: chain: one of "base", "ethereum", "bnb". agent_id: the numeric ERC-8004 agent id. Returns reachability, TLS validity, x402 support, payments-received (boolean only), MCP tool count, OpenAPI method count, well-known presence, owner-named (boolean), and a neutral status label (Live & monetized / Live, no payments / Stub or unreachable). No owner identity string and no payment amounts — those are paid. Returns an `error` field if the agent is not indexed. Use this to vet a counterparty agent before transacting. Required: chain, agent_id.
get_coverage_stats- Live coverage of the ERC-8004 agent economy across Base, Ethereum and BNB Chain. Returns counts only: how many agents are indexed, how many expose a live MCP server / OpenAPI / well-known card, total MCP tools and OpenAPI methods observed, contracts verified, EOAs and owners identified, plus a per-chain breakdown. No names, addresses, or handles. Use this to size the market and see where capability density is growing.
get_leaderboards- Top ERC-8004 agents by live capability, plus the most recently indexed. Three ranked lists — top by live MCP tool count, top by OpenAPI method count, and most-recently indexed — each with agent_id, chain, public name, a shareable detail URL, and the relevant count. Names and counts only: no owner wallets, handles, or endpoint URLs. Use this to find the most capable / most active agents to integrate or watch.
get_network_teaser- A capped teaser of the on-chain agent-to-agent payment graph. Returns connected agents (nodes) and the value flowing between them (edges), capped to a small connected sample (≤200 nodes). This is a truncated preview, not the full network. Use it to see who pays whom in the agent economy; the full graph — every node and edge with amounts — is the paid endpoint below.
Last successful function declaration observed on . Source: https://api.onchainagentintel.io/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.onchainagentintel.io/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.8.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-15 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-15 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.onchainagentintel.io | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | api.onchainagentintel.io |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json