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.
npx agentmods add mcp/0xendale/evm-agent-toolkit/evm-agent-toolkitgit clone --depth 1 https://github.com/0xendale/evm-agent-toolkitWrote 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/0xendale/evm-agent-toolkit/evm-agent-toolkit)<a href="https://agentmods.dev/mcp/0xendale/evm-agent-toolkit/evm-agent-toolkit"><img src="https://agentmods.dev/badge/mcp/0xendale/evm-agent-toolkit/evm-agent-toolkit.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
evm-agent-toolkit 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 4d 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
{ "evm-agent-toolkit": { "command": "npx", "args": [ "-y", "@0xendale/evm-agent-toolkit" ] } }
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.
- 4d ago First seen · 9 lines scan A a5e1aab47be0
evm-agent-toolkit is an MCP server published in the GitHub repository 0xendale/evm-agent-toolkit (1 stars, last pushed 1mo 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
evmole
Local structured analysis of deployed EVM runtime bytecode. Runs locally from the evmole-mcp npm package.
x402-base-mcp
Read-only Base mainnet reader. Verifies x402 payment settlements + AFTA federation status. Runs locally from the @tensorfeed/x402-base-mcp npm package. Needs 1 environment variable to run.
nodeflare-mcp
Blockchain JSON-RPC on 23 EVM chains for AI agents - free tier, API key, or x402 pay-per-call. Runs locally from the nodeflare-mcp npm package. Needs 2 environment variables to run.
nodeflare
MCP server for NodeFlare RPC — blockchain data on 23 EVM chains for AI agents. Free public tier, API key, or pay-per-call with x402 (USDC on Base/Polygon/Arbitrum). Runs locally from the nodeflare-mcp npm package.
agentic-vault
Server-side EVM signing with AWS KMS and built-in DeFi protocol awareness. Expose your wallet to AI agents via MCP, CLI, or OpenClaw. Runs locally from the @agenticvault/agentic-vault npm package.
suwappu
Cross-chain DEX for AI agents. Swap tokens across 7+ chains. Runs locally from the @suwappu/mcp-server npm package. Needs 1 environment variable to run.