Skip to content
Onchain Agent Intel logo

Onchain Agent Intel MCP server

Which servers in the official MCP registry are Onchain Agent Intel's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Onchain Agent Intel

Whose server it is
  • Registry nameio.onchainagentintel/agent-zero-intelverified in the MCP registry

The registry name sits under onchainagentintel.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools6
  • Server calls itselfagent-zero-intel
  • Server version1.8.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 96 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Check whether an AI agent is live before paying it; Review an agent's on-chain reputation before transacting with it; See which agents are earning payments and who pays them.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "Check whether an AI agent is live before paying it", the likely first call is get_agent_summary.
  • For "Review an agent's on-chain reputation before transacting with it", the likely first call is agent_trust_teaser.
  • For "See which agents are earning payments and who pays them", the likely first call is get_network_teaser.
  • Parameters are untyped or undescribed in 3 of 6 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer222 ms
  • Space in an agent's context≈ 1,953 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsB · 75 of 100
  • Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 3 of 6
  • Not saying whether it only reads or can destroy: 6 of 6

What an agent can do with it

  • can do · Check whether an AI agent is live before paying it
  • can do · Review an agent's on-chain reputation before transacting with it
  • can do · See which agents are earning payments and who pays them

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-26
  • get_coverage_stats

    Live coverage of the ERC-8004 agent economy across Base and Ethereum. 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…

  • 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…

  • get_agent_summary

    Objective, counts-only signals for one ERC-8004 agent. Args (BOTH OPTIONAL — call with `{}` to see Agent Zero itself): chain: one of "base", "ethereum". Default: "base". agent_id: the numeric ERC-8004 agent id. Default: 19353 (Agent Zero…

  • 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…

  • agent_trust_teaser

    Credit-score-style TEASER for one ERC-8004 agent's trust profile. Args (BOTH OPTIONAL — call with `{}` to see Agent Zero itself): chain: one of "base", "ethereum". Default: "base". agent_id: the numeric ERC-8004 agent id. Default: 19353…

  • list_payable_x402_endpoints

    Directory of ERC-8004 agents that answered a well-formed HTTP 402 x402 challenge during our last field probe. OBSERVATION ONLY — not a score, ranking, or endorsement. Args (ALL OPTIONAL — call with `{}` for the top 10 across both chains)…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "agent-zero-intel": {
      "type": "http",
      "url": "https://api.onchainagentintel.io/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http onchainagentintel https://api.onchainagentintel.io/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.onchainagentintel.io/mcp as a custom connector in the settings.

OpenAPI spec

25 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.