ERC-8126 Scan
REMOTE · ERC8126SCAN.AI
378k+ ERC-8004 agents and their security verifications. Two tools free, the rest USDC over x402.
Available components
Last scanned (40 minutes ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 819 tokens (~136/item across 6 items; 6 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Aug 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://erc8126scan.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=erc8126scan.ai | CN=WE1,O=Google Trust Services,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3e25a69c4757227d0efbfb144980a07b |
| SANs: erc8126scan.ai, *.erc8126scan.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of erc8126scan.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| erc8126scan.ai. | present | 2371 | 13 | Verified |
| erc8126scan.ai. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://erc8126scan.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://erc8126scan.ai/api/mcp | HTTPS enforced | 301 | https://erc8126scan.ai/api/mcp |
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 Get agent detail ~95
Fetch the full detail record for a single agent by UUID, including verification state and metadata. Judge the agent by `risk_level`, not the raw overall_risk_score: 'not_verified' means nobody has paid to assess it yet and scores 100 by presumption, which is not a finding against the agent. Costs $0.001 USDC per call when paying with x402.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Agent UUID. |
No output schema declared.
No examples provided.
get_agent_activity Get agent activity ~58
Fetch on-chain activity and liveness signals for one agent, including whether it is currently active and when it was last checked. Costs $0.002 USDC per call when paying with x402.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Agent UUID. |
No output schema declared.
No examples provided.
get_agent_report Get agent security report ~98
Fetch the full security assessment report for one agent: per-dimension findings, evidence and recommendations. Returns data only for agents owned by the caller — the wallet bound to your API key, or the wallet that paid via x402. Other agents return FORBIDDEN_NOT_OWNER. Use get_agent for public scores on any agent. Costs $0.05 USDC per call when paying with x402.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Agent UUID. |
No output schema declared.
No examples provided.
get_index_stats Index coverage ~66
Free. How much of the ERC-8004 agent population this index covers: total agents synced from the on-chain Identity Registry, and how many carry verification results. Use it to judge whether the index is likely to know about the agent you care about before paying to look it up.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services List services and prices ~69
Free. The catalogue: every tool on this server, what it returns, what it costs per call, and how to read the risk fields. Call this first — it is authoritative about pricing, needs no payment, key or wallet, and answers most questions about what this server can do without spending anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_agents Search agents ~324
Search and filter scanned ERC-8004 agents by chain, risk score range, and verification status. Returns a paginated list with per-dimension scores (ETV, MCV, SCV, WAV, WV) and an overall risk score. Pass `wallet` or `id` to look up a single agent directly. IMPORTANT: read `risk_level`, not `overall_risk_score`, to judge an agent. Scoring presumes risk, so an agent nobody has paid to verify scores 100 exactly like one assessed as dangerous. risk_level separates them: 'not_verified' means unassessed and is NOT a finding against the agent, while 'critical' means verified and genuinely high risk. Most indexed agents are 'not_verified'. Costs $0.001 USDC per call when paying with x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Filter by chain, e.g. 'base', 'ethereum'. |
| id | string | – | Look up one agent by its UUID. |
| limit | integer | – | Page size. Capped by your plan tier. |
| max_score | integer | – | Maximum overall risk score (0-100). |
| min_score | integer | – | Minimum overall risk score (0-100). |
| order | string | – | Sort direction. Defaults to desc. |
| page | integer | – | Page number, 1-indexed. |
| sort | string | – | Sort field. Defaults to created_at. |
| verified | string | – | Filter by verification status. |
| wallet | string | – | Look up one agent by registrant or agent wallet address. |
No output schema declared.
No examples provided.
How do I install the ERC-8126 Scan MCP server?
ERC-8126 Scan is a hosted endpoint at https://erc8126scan.ai/api/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 · erc8126scan.ai
claude mcp add --transport http uk-co-cybercentry-erc-8126-scan 'https://erc8126scan.ai/api/mcp'
What is the ERC-8126 Scan MCP server?
ERC-8126 Scan is an MCP server listed in the public MCP registry as uk.co.cybercentry/erc-8126-scan. 378k+ ERC-8004 agents and their security verifications. Two tools free, the rest USDC over x402. This page covers its hosted endpoint (https://erc8126scan.ai/api/mcp).
Is the ERC-8126 Scan MCP server safe to use?
ERC-8126 Scan scores 87 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 ERC-8126 Scan MCP server expose?
ERC-8126 Scan exposes 6 tools: list_services, get_index_stats, search_agents, get_agent, get_agent_activity, get_agent_report. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.
Does the ERC-8126 Scan MCP server require authentication?
No. We connected to ERC-8126 Scan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ERC-8126 Scan MCP server still maintained?
ERC-8126 Scan is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.