Agent Zero — ERC-8004 Trust Filter

io.onchainagentintelPublished by onchainagentintel.ioOfficial publisherv1.9.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Lets an assistant check ERC-8004 agent trust signals, filtering endpoints by whether they have reached a threshold of payers.

What you can do
It acts as a trust filter for ERC-8004, the on-chain agent registry, and reports on x402 endpoint activity. The description states that only about 3.8% of x402 endpoints reach five or more payers in 30 days, which is the kind of signal it surfaces. It is offered as a free MCP with an x402 upgrade path. No individual tools are listed in the manifest.
When to use it
Worth considering when an assistant needs to judge whether an ERC-8004 or x402 agent endpoint looks trustworthy based on payer activity before interacting with it. Less useful if you do not work with on-chain agents or x402 payments. The sparse documentation means you should test it before relying on it.
Requirements
A remote streamable HTTP endpoint at the provider's API host; no local runtime, package, environment variables, or headers are declared. No authentication is declared, and network access to the provider is required.
Before you install
The description is minimal and no tools, authentication, or data-handling details are published, so what the server reads or returns cannot be verified from the listing. It is a remote endpoint, meaning requests go to a third-party host. The description mentions an x402 upgrade, which may involve on-chain payments; confirm any cost before using paid features.

Installation

In SourceWeft

  1. Open Agent Zero — ERC-8004 Trust Filter in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.onchainagentintel%2Fagent-zero-intel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agent-zero-erc-8004-trust-filter": {
      "type": "http",
      "url": "https://api.onchainagentintel.io/mcp"
    }
  }
}

Tools

6

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 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.

Takes no parameters.

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. 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.

Takes no parameters.

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, 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 to the owner wallet and to the agent's own address (booleans only: payments_to_owner_wallet, payments_to_agent_address, payment_attribution; payments_received is deprecated, sunset 2026-11-07), MCP tool count, OpenAPI method count, well-known presence, owner-named (boolean), and a neutral status label (status_label_v2: Reachable, payment signals / Reachable, no payment signals / Stub or unreachable; the old status_label is deprecated, sunset 2026-11-07). 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 reviews-from-paid-jobs (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.

Parameterschainagent_id

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. 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.

Takes no parameters.

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 (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. Agents that belong to a platform registering many agents and have no endpoint or activity of their own yet also carry `platform_listed: true` and `platform`, with bucket Platform-listed. 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 reviews-from-paid-jobs (commerce-backed) breakdown. Every response from this free tool carries an `unlock` + `paid_upgrade` block with the exact paid endpoint, price, and payment discovery.

Parameterschainagent_id

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): 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.

Parameterschainlimit

Version history

1
  1. v1.9.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.