Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Cybercentry/erc-8126-scan-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/cybercentry/erc-8126-scan-mcp/erc-8126-scan)<a href="https://agentmods.dev/mcp/cybercentry/erc-8126-scan-mcp/erc-8126-scan"><img src="https://agentmods.dev/badge/mcp/cybercentry/erc-8126-scan-mcp/erc-8126-scan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/cybercentry/erc-8126-scan-mcp/erc-8126-scan"><img src="https://agentmods.dev/badge/mcp/cybercentry/erc-8126-scan-mcp/erc-8126-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
erc-8126-scan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"erc-8126-scan": {
"url": "https://erc8126scan.ai/api/mcp",
"type": "streamable-http"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 6 lines scan A e67732e11325
erc-8126-scan is an MCP server published in the GitHub repository Cybercentry/erc-8126-scan-mcp (0 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
verification
Twelve tools: token, wallet, contract and site security. Two free, the rest $1 in USDC over x402. Remote server at centry.cybercentry.co.uk.
mcp
Elytra Security as a Model Context Protocol server. Gives your AI agent access to Elytra's hosted scanning surface — 180 detectors, including 12 famous-hack patterns and Base-native wallet/payment/DeFi checks. Returns public Elytra receipts with EAS attes. Runs locally from the @elytrasec/mcp npm package.
aikido-mcp
Security analysis for Aiken smart contracts on Cardano. 75 vulnerability detectors. Runs locally from the aikido-mcp npm package. Needs 1 environment variable to run.
strategy-lab
Stress-test lowcap, perp and LP strategies. Returns the full distribution and a reproduction seed. Remote server at kellyruns.xyz.
onchain-agent-wallets
Give an AI agent a Solana spending allowance instead of your key. Chain-enforced cap, x402. Runs locally from the @three-ws/onchain-agent-wallets npm package. Needs 5 environment variables to run.
chainstack
Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds. Remote server at mcp.chainstack.com.