ERC-8126 Scan MCP Server
Enables users to search the on-chain index of 378,000+ ERC-8004 agents and read Cybercentry verification results spanning token, code, media, web, and wallet dimensions.
README
ERC-8126 Scan MCP Server
Security intelligence for ERC-8004 agents: search the on-chain agent index and read verification results.
Nothing to install. This is a remote MCP server — connect to the URL and the tools appear.
| Endpoint | https://erc8126scan.ai/api/mcp |
| Transport | streamable-http |
| Registry | uk.co.cybercentry/erc-8126-scan |
| Website | https://erc8126scan.ai |
What it is
Every agent minted in the ERC-8004 Identity Registry is indexed automatically — 378,000+ and counting. Each one carries verification results across five dimensions, produced by the Cybercentry verification services:
| Dimension | What it covers | |
|---|---|---|
| ETV | Token verification | The agent's token contract |
| SCV | Solidity code verification | The staking contract source |
| MCV | Media content verification | C2PA provenance of the agent's image |
| WAV | Web application verification | The agent's live site or dApp frontend |
| WV | Wallet verification | OFAC sanctions screening and funding-chain risk |
This server exposes that index. It does not run verifications — it serves results already computed and stored.
Connect
Claude (Desktop or claude.ai)
Remote servers are added as connectors, not through claude_desktop_config.json — that file is for local servers that run a command.
- Settings → Connectors
- Add → Add custom connector
- Paste
https://erc8126scan.ai/api/mcp
Other clients
Anything that speaks MCP over streamable HTTP can connect. Point it at:
https://erc8126scan.ai/api/mcp
Check your client's own documentation for where a remote MCP server URL goes — some use a settings pane, some a config file. If yours takes a config file, the field is the server URL rather than a command.
Tools
Six tools, all read-only. None of them mints, writes on-chain, or spends your credits.
Two are free — no payment, wallet or account:
| Tool | What it returns |
|---|---|
list_services |
The catalogue: every tool, its price, and how to read the risk fields |
get_index_stats |
How many agents are indexed, so you can judge coverage before paying |
The other four are paid:
| Tool | What it returns | Per call | Plan |
|---|---|---|---|
search_agents |
Filter the index by chain, risk score range and verification status; paginated | $0.001 | Starter |
get_agent |
Full detail for one agent by UUID | $0.001 | Starter |
get_agent_activity |
On-chain activity and liveness for one agent | $0.002 | Starter |
get_agent_report |
Full security assessment: per-dimension findings and evidence | $0.05 | Pro |
Call list_services first. It is free, and authoritative about current pricing.
get_agent_report returns data only for agents owned by the wallet bound to your API key. Other agents return FORBIDDEN_NOT_OWNER. Public scores for any agent are available through get_agent.
Tools you cannot reach on your plan are hidden from tools/list rather than listed and refused.
Reading the scores
Judge an agent by risk_level, not overall_risk_score.
Scoring presumes risk: a check that applies to an agent but has not been verified counts as 100. So an agent nobody has paid to assess scores exactly the same as one assessed and found dangerous. Most of the index is the former.
risk_level separates them:
| Value | Meaning |
|---|---|
not_verified |
Nobody has assessed this agent yet. Not a finding against it. |
not_assessed |
No score recorded |
low / moderate / elevated / high |
Verified, scoring in that band |
critical |
Verified and genuinely high risk |
Treating a not_verified agent as dangerous is the most common way to misread this data.
Paying
Two free tools, then two ways to pay for the rest. tools/list is public, so an agent can see everything on offer and what it costs before deciding to pay for anything.
x402 — no account, no key. The client is quoted a price, pays in USDC, and retries. Pay on whichever chain you hold funds on:
Base eip155:8453 USDC
Solana mainnet USDC
| Tool | Per call |
|---|---|
list_services |
free |
get_index_stats |
free |
search_agents |
$0.001 |
get_agent |
$0.001 |
get_agent_activity |
$0.002 |
get_agent_report |
$0.05 |
An unpaid call returns a JSON-RPC error with code 402, carrying the payment requirements in error.data — the same shape as the Cybercentry verification server.
API key — for volume, or clients that do not speak x402 yet. Pass an erc8126_ key as a bearer token:
Authorization: Bearer erc8126_...
Keys come from erc8126scan.ai/my-api-keys. Calls draw on your plan's daily quota instead of being paid for individually, and tool availability and page sizes follow your tier. A key that is presented but invalid is rejected outright rather than quietly falling back to per-call billing.
Either way, get_agent_report is scoped to agents owned by the caller — the wallet bound to your key, or the wallet that paid.
Standards
- ERC-8004 — Trustless Agents, the Identity Registry this index reads
- ERC-8126 — AI Agent Verification (Final)
- ERC-8196 — AI Agent Authenticated Wallet (Final)
Links
- Endpoint — https://erc8126scan.ai/api/mcp
- Site — https://erc8126scan.ai
- API keys — https://erc8126scan.ai/my-api-keys
- Cybercentry verification MCP — https://github.com/Cybercentry/verification-mcp
Cybercentry Limited
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.