Security intelligence for ERC-8004 agents, as a remote MCP server. Search 378k+
Security intelligence for ERC-8004 agents, as a remote MCP server. Search 378k+ indexed agents and read Cybercentry verification results.
active Production-safe Score 92/100 http no auth
At a glance
| Endpoint | https://erc8126scan.ai/api/mcp |
|---|---|
| Source | https://github.com/Cybercentry/erc-8126-scan-mcp |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-08-22 21:04:47 |
| Last checked | 2026-11-17 21:53:53 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 624 / 913 ms |
| Last successful check | 2026-11-17 21:53:53 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
list_services— 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 —get_index_stats— Free. How much of the ERC-8004 agent population this index covers: total agents synced from the on-chain Identity Registry, and how many carsearch_agents— Search and filter scanned ERC-8004 agents by chain, risk score range, and verification status. Returns a paginated list with per-dimension sget_agent— Fetch the full detail record for a single agent by UUID, including verification state and metadata. Judge the agent by `risk_level`, not theget_agent_activity— Fetch on-chain activity and liveness signals for one agent, including whether it is currently active and when it was last checked. Costs $0.get_agent_report— Fetch the full security assessment report for one agent: per-dimension findings, evidence and recommendations. Returns data only for agents
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:53:53 | ✓ | ✓ | 507 ms | 90 | active |
| 2026-11-17 21:38:44 | ✓ | ✓ | 1032 ms | 87 | active |
| 2026-11-17 21:23:27 | ✓ | ✓ | 554 ms | 90 | active |
| 2026-11-17 21:08:13 | ✓ | ✓ | 724 ms | 90 | active |
| 2026-11-17 20:53:11 | ✓ | ✓ | 477 ms | 90 | active |
| 2026-11-17 20:38:10 | ✓ | ✓ | 553 ms | 90 | active |
| 2026-11-17 20:23:07 | ✓ | ✓ | 591 ms | 90 | active |
| 2026-11-17 20:08:00 | ✓ | ✓ | 798 ms | 90 | active |
| 2026-11-17 19:52:09 | ✓ | ✓ | 682 ms | 90 | active |
| 2026-11-17 19:37:01 | ✓ | ✓ | 569 ms | 90 | active |
| 2026-11-17 19:21:51 | ✓ | ✓ | 611 ms | 90 | active |
| 2026-11-17 19:06:38 | ✓ | ✓ | 706 ms | 90 | active |
| 2026-11-17 18:51:25 | ✓ | ✓ | 539 ms | 90 | active |
| 2026-11-17 18:36:20 | ✓ | ✓ | 632 ms | 90 | active |
| 2026-11-17 18:21:16 | ✓ | ✓ | 731 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://erc8126scan.ai/api/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/erc8126scan-ai-api-mcp # JSON