Skip to content

Agent Zero — ERC-8004 Trust Filter

by onchainagentintel.io · remote · no sign-in to list tools · v1.9.0 · published by io.onchainagentintel

Trust filter for ERC-8004: only ~3.8% of x402 endpoints hit 5+ payers/30d. Free MCP; x402 upgrade.

Changes · 1

6 tools: 1 change things and 5 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 1Claude Code: ask
  • agent_trust_teaserCredit-score-style TEASER for one ERC-8004 agent's trust profile.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 (Agent Zero, the agent serving this MCP endpoint). Example: `{}` returns Agent Zero on base; `{"chain": "base", "agent_id": 19353}` is the explicit form. By construction returns ONLY: name, chain, agent_id, public readiness_bucket, and a 1-line verdict headline. Every decision-driving value — trust_verdict, readiness_score, risk_flags, money-flow details, counterparty list, full score breakdown — is redacted as `null` and enumerated in the `locked` map. The response carries the exact paid endpoint URL (/v1/intel/agent/{agent_id}?chain={chain}), the x402 price as currently configured, and a one-line how-to-pay-via-x402 hint. Returns `error` with the same unlock pointer if the agent is not indexed, so a caller probing an unknown id still sees how to pay for a known one. Paid counterpart: `GET /v1/intel/agent/{agent_id}?chain={chain}` (x402, USDC on base-mainnet) returns the full trust verdict (safe_to_transact / caution / avoid / insufficient_data), readiness_score + sub-scores, Sybil-adjusted reputation, and the commerce-backed money-flow breakdown. Every response from this free tool carries an `unlock` + `paid_upgrade` block with the exact paid endpoint, price, and payment discovery.
Only reads 5Claude Code: allow
  • get_agent_summaryObjective, counts-only signals for one ERC-8004 agent.No findings

    Why it is in this group

    • The name "get_agent_summary" says "get": a word for reading.
    Description, as the server wrote it
    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, the agent serving this MCP endpoint). Example: `{}` returns Agent Zero on base; `{"chain": "base", "agent_id": 19353}` is the explicit form. 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. Paid counterpart: `GET /v1/intel/agent/{agent_id}?chain={chain}` (x402, USDC on base-mainnet) unlocks trust_verdict (safe_to_transact / caution / avoid / insufficient_data), readiness_score, Sybil-adjusted reputation, and the commerce-backed breakdown — the decision-driving values this free response returns as `null` inside a `locked` map. Every response carries an `unlock` block with the exact paid endpoint, price, and payment discovery.
  • get_coverage_statsLive coverage of the ERC-8004 agent economy across Base and Ethereum.No findings

    Why it is in this group

    • The name "get_coverage_stats" says "get": a word for reading.
    Description, as the server wrote it
    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 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. Paid counterpart: `GET /v1/intel/market` (x402, USDC on base-mainnet) returns the full capability market map — which capabilities are saturated vs open, per-capability agent lists, and momentum. Every response from this free tool carries an `unlock` block with the exact paid endpoint, price, and payment discovery.
  • get_leaderboardsTop ERC-8004 agents by live capability, plus the most recently indexed.No findings

    Why it is in this group

    • The name "get_leaderboards" says "get": a word for reading.
    Description, as the server wrote it
    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. Paid counterpart: `GET /v1/intel/trending` (x402, USDC on base-mainnet) returns trending intel — top earners, fastest-rising agents, and integration candidates ranked with the signals behind the ranking. Every response from this free tool carries an `unlock` block with the exact paid endpoint, price, and payment discovery.
  • get_network_teaserA capped teaser of the on-chain agent-to-agent payment graph.No findings

    Why it is in this group

    • The name "get_network_teaser" says "get": a word for reading.
    Description, as the server wrote it
    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. Paid counterpart: `GET /v1/intel/graph` (x402, USDC on base-mainnet) returns the full agent-to-agent payment graph — every node and edge with USDC/ETH amounts and no node cap. Every response from this free tool carries an `unlock` block with the exact paid endpoint, price, and payment discovery.
  • list_payable_x402_endpointsDirectory of ERC-8004 agents that answered a well-formed HTTP 402 x402 challenge during our last field probe.No findings

    Why it is in this group

    • The name "list_payable_x402_endpoints" says "list": a word for reading.
    Description, as the server wrote it
    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): chain: one of "base", "ethereum" (omit for both). Default: null. limit: 1..10 rows (free-tier cap). Default: 10. Returns per-row raw probe facts: agent_id, chain, endpoint_url, http_402_ok, network, asset, price_usd as the challenge advertised, payTo_present (boolean — the actual address is paid), sibling_agent_ids (other ERC-8004 ids served by the same gateway row — the 'shared operator' cue), probed_at. Plus `total_endpoints_valid_402` and `total_agents_valid_402` so a caller can see what fraction of the surface this free slice covers. Source: the 0946 field-test one-shot probe (unauthenticated, read-only, no payment signed). See the `field_test_url` field for the full writeup. Paid counterpart: the paid x402 /v1/intel/* endpoints return the same-origin enriched intel on any single agent in this list — owner identity, payment history, peers, trust verdict, Sybil-adjusted reputation. Every response from this free tool carries an `unlock` + `paid_upgrade` block with the exact paid endpoint, price, and payment discovery.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.9.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agent-zero-intel__get_coverage_stats",
      "mcp__agent-zero-intel__get_leaderboards",
      "mcp__agent-zero-intel__get_agent_summary",
      "mcp__agent-zero-intel__get_network_teaser",
      "mcp__agent-zero-intel__list_payable_x402_endpoints"
    ],
    "ask": [
      "mcp__agent-zero-intel__agent_trust_teaser"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as agent-zero-intel. Review it before you use it.