Agent Zero — ERC-8004 Trust Filter
REMOTE · API.ONCHAINAGENTINTEL.IO · SCANNED SEP 20
Trust filter for ERC-8004: only ~3.8% of x402 endpoints hit 5+ payers/30d. Free MCP; x402 upgrade.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 838 tokens (~209/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Agent Zero — ERC-8004 Trust Filter MCP server?
Agent Zero — ERC-8004 Trust Filter is a hosted endpoint at https://api.onchainagentintel.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.onchainagentintel.io
claude mcp add --transport http io-onchainagentintel-agent-zero-intel 'https://api.onchainagentintel.io/mcp'
{
"mcpServers": {
"io-onchainagentintel-agent-zero-intel": {
"url": "https://api.onchainagentintel.io/mcp"
}
}
} {
"servers": {
"io-onchainagentintel-agent-zero-intel": {
"type": "http",
"url": "https://api.onchainagentintel.io/mcp"
}
}
} [mcp_servers.io-onchainagentintel-agent-zero-intel] url = "https://api.onchainagentintel.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-onchainagentintel-agent-zero-intel": {
"type": "remote",
"url": "https://api.onchainagentintel.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-onchainagentintel-agent-zero-intel --url 'https://api.onchainagentintel.io/mcp' --transport streamable-http
mcp_servers:
io-onchainagentintel-agent-zero-intel:
url: "https://api.onchainagentintel.io/mcp" {
"McpServers": {
"io-onchainagentintel-agent-zero-intel": {
"Transport": "http",
"Url": "https://api.onchainagentintel.io/mcp"
}
}
} assistant mcp add io-onchainagentintel-agent-zero-intel -t streamable-http -u 'https://api.onchainagentintel.io/mcp'
{
"mcpServers": {
"io-onchainagentintel-agent-zero-intel": {
"type": "http",
"url": "https://api.onchainagentintel.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 −2
- Tool “get_agent_summary” rewrote its description, which is the text the model reads security
- Tool “get_coverage_stats” rewrote its description, which is the text the model reads security
- Tool “get_leaderboards” rewrote its description, which is the text the model reads security
- Tool “get_network_teaser” rewrote its description, which is the text the model reads security
- Schema quality: 138 → 209 ▼ functional
- 4 Sept 26 0
- Stability: 0.97 → pass security
- 3 Sept 26 0
- Stability: pass → 0.97 functional
- 31 Aug 26 0
- Stability: 0.97 → pass security
- 30 Aug 26 0
- Stability: pass → 0.97 functional
- 27 Aug 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.onchainagentintel.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onchainagentintel.io | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6553be9b2f6b033004a73964fbe195406dc |
| SANs: *.onchainagentintel.io, onchainagentintel.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.onchainagentintel.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| onchainagentintel.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.onchainagentintel.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.onchainagentintel.io/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_agent_summary ~261
Objective, counts-only signals for one ERC-8004 agent. Args: chain: one of "base", "ethereum". 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. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | yes | – |
| chain | string | yes | – |
No output schema declared.
No examples provided.
get_coverage_stats ~167
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_leaderboards ~175
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_network_teaser ~144
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Agent Zero — ERC-8004 Trust Filter MCP server?
Agent Zero — ERC-8004 Trust Filter is an MCP server listed in the public MCP registry as io.onchainagentintel/agent-zero-intel. Trust filter for ERC-8004: only ~3.8% of x402 endpoints hit 5+ payers/30d. Free MCP; x402 upgrade. This page covers its hosted endpoint (https://api.onchainagentintel.io/mcp).
Is the Agent Zero — ERC-8004 Trust Filter MCP server safe to use?
Agent Zero — ERC-8004 Trust Filter scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Zero — ERC-8004 Trust Filter MCP server expose?
Agent Zero — ERC-8004 Trust Filter exposes 4 tools: get_coverage_stats, get_leaderboards, get_agent_summary, get_network_teaser. Their descriptions and schemas cost roughly 747 tokens of context every time the server is loaded.
Does the Agent Zero — ERC-8004 Trust Filter MCP server require authentication?
No. We connected to Agent Zero — ERC-8004 Trust Filter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Zero — ERC-8004 Trust Filter MCP server still maintained?
Agent Zero — ERC-8004 Trust Filter is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.