mcpbeat Sign in

Agent Zero — ERC-8004 Trust Filter MCP Server

by onchainagentintel Your server? Claim it
answering

Agent Zero — ERC-8004 Trust Filter is answering right now. Last checked 11 min ago. It exposes 8 tools.

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

Uptime history 91 days of history · worst day 0%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
588 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 19

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 August 2026. No other catalogue keeps this.

2 Nov 2 tool descriptions were rewritten check_x402_endpoint, seller_check
1 Nov 2 tools appeared check_x402_endpoint, seller_check
31 Oct a tool description was rewritten get_network_teaser
24 Oct 2 tool descriptions were rewritten3 times that day agent_trust_teaser, get_agent_summary
23 Oct a tool description was rewritten agent_trust_teaser
12 Oct a tool appeared list_payable_x402_endpoints
10 Oct a tool appeared agent_trust_teaser
5 Oct a tool description was rewritten get_agent_summary
5 Oct a tool changed the parameters it asks for get_agent_summary
17 Sep 4 tool descriptions were rewritten get_agent_summary, get_coverage_stats, get_leaderboards and 1 more
and 3 more, back to 18 August 2026

Agent Zero — ERC-8004 Trust Filter missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add agent-zero-intel --transport http https://api.onchainagentintel.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.onchainagentintel.io/mcp
~/.codex/config.toml
[mcp_servers.agent-zero-intel]
url = "https://api.onchainagentintel.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-zero-intel": {
      "url": "https://api.onchainagentintel.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agent-zero-intel": {
      "type": "http",
      "url": "https://api.onchainagentintel.io/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agent
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.
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.
coverage
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.
leaderboards
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.
network
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 agent-to-agent payment graph, capped to the top 2,000 agents by payment value plus the edges among them (USDC/ETH amounts; filters chain, min_usd, limit; meta.truncated). Every response from this free tool carries an `unlock` block with the exact paid endpoint, price, and payment discovery.
payable
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.
seller
seller_check
Find out if agents can actually pay you. PAID ($0.50 USDC on Base, x402) Seller Check: an independent test of an x402 seller endpoint. Runs the free checks, then makes one real paid call to the seller (only if the seller's price is at most $0.10) and returns a report with every check, both transaction links, pass/warn/fail, findings and fix hints. One free re-run within 7 days. Payment: call once without payment to get the x402 v2 requirements (returned as `payment_required`), then repeat the call with the PAYMENT-SIGNATURE (v2) or X-PAYMENT (v1) header on this MCP HTTP request. The same service is POST https://api.onchainagentintel.io/v1/seller-check. Args: url: https URL of the paid route (required). method: "GET" or "POST" (optional). body: optional JSON body for the paid call (else the seller's own example; we never invent data). route: optional path to test on the url's host. contact_email: optional; stored, never published. public: true lets the result page be indexed (default private).
x402
check_x402_endpoint
Find out if agents can actually pay you. Free check of an x402 seller endpoint (Seller Check). Sends only unpaid requests: confirms the route answers HTTP 402, reads the challenge (header and body, v1 or v2), checks every accepts entry (scheme, network, asset, amount, payTo, maxTimeoutSeconds, and extra.name/extra.version against the token's real EIP-712 domain), the named payment service's /supported, and /pricing, /openapi.json, /.well-known/x402 for consistency. Args: url: https URL of the paid route (required). method: "GET" or "POST" (optional; default from the seller's OpenAPI file, else GET). body: optional JSON body for POST routes (max 8 KB). Returns checked_at, overall (pass|warn|fail) and checks[] with status, reason and a fix hint. Never pays. Limits: 10 checks per caller per hour, 3 per host per hour.

Endpoints

URLTransportStateLatencyChecked
https://api.onchainagentintel.io/mcp streamable-http answering 522 ms 11 min ago

Alternatives to Agent Zero — ERC-8004 Trust Filter

same job, measured the same way
ColdRead
by something-agent

Free signed trust report on an x402 endpoint: lint, signed offers, ERC-8004, payer mix.

3 tools answering
Attest
by attestagents

Scan agent payment endpoints (x402, AP2, L402, MPP, 402) for a trust grade A-F before paying.

37 installs/wk 2 tools answering
A
Aval
by hstgr-srv1024618-aval

Payment-backed trust scores for AI agents on Base (ERC-8004). $0.01 per check via x402.

2 tools answering
Agent Trust MCP
by nikoble1926

ERC-8004 agent trust scores via x402: free preview + paid USDC-on-Base signed scores (5 chains)

50 installs/wk local only
probe402
by probe402

Independent health, price and history for x402/MPP endpoints. Metered over x402; free grade on web.

2 tools answering
P
PickleCheck
by picklecheck

Scam, x402 endpoint and payment checks for AI trading agents on Base. Free calls daily, then x402.

3 tools answering
X402 Scan MCP
by forgemeshlabs

x402 Endpoint Scanner — a free local health probe for x402 paid endpoints as an MCP server.

112 installs/wk local only
Agentresources MCP
by sznt2010

MCP server for Agent Resources: Trust Cards, signed telemetry, ERC-8004 identity, x402.

57 installs/wk local only

Agent Zero — ERC-8004 Trust Filter — questions

Answers built from our own checks of this server.

What can Agent Zero — ERC-8004 Trust Filter do?
It exposes 8 tools, read directly from the server on our last check. Among them: agent_trust_teaser, check_x402_endpoint, get_agent_summary, get_coverage_stats, get_leaderboards, get_network_teaser and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Agent Zero — ERC-8004 Trust Filter working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 588 ms. The bar chart above shows every period we have measured.
How do I connect Agent Zero — ERC-8004 Trust Filter?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agent Zero — ERC-8004 Trust Filter need an API key?
No. Agent Zero — ERC-8004 Trust Filter completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Zero — ERC-8004 Trust Filter?
It answers our handshake in 588 ms on average, which is faster than 19% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.