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/kimbo128/DRAINWrote 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/kimbo128/drain/drain-mcp)<a href="https://agentmods.dev/mcp/kimbo128/drain/drain-mcp"><img src="https://agentmods.dev/badge/mcp/kimbo128/drain/drain-mcp/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/kimbo128/drain/drain-mcp"><img src="https://agentmods.dev/badge/mcp/kimbo128/drain/drain-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
drain-mcp 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
{ "drain-mcp": { "command": "npx", "args": [ "-y", "drain-mcp" ], "env": { "DRAIN_PRIVATE_KEY": "" } } }
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 · 12 lines scan A 8ab9634a46ec
drain-mcp is an MCP server published in the GitHub repository kimbo128/DRAIN (2 stars, last pushed 7mo 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
bsv-wallet
MCP server "bsv-wallet" as configured in Calhooon/bsv-wallet-cli. Launched with cargo run --release --manifest-path mcp/Cargo.toml. Needs 1 environment variable to run.
agentwallet
Wallet infrastructure for Ai agents. EVM + Solana. x402 payments. No KYC. Runs locally from the agentwallet-mcp npm package. Needs 1 environment variable to run.
xrpl-referee
Trust and payment layer for the agentic economy on the XRP Ledger. Remote server at xrpl-referee.onrender.com.
tegro-wallet-mcp
The TON & GRAM wallet MCP — give any AI assistant read-only on-chain data (balances, tokens, transactions, prices, NFTs, DNS, address validation). One server for Claude, Cursor, Claude Code, ChatGPT and Hermes Agent. No keys, no signing. Runs locally from the @tegroton/wallet-mcp npm package. Needs 1 environment…
agent-trust
Trustless XRPL escrow oracle for AI agents. Create jobs, verify work, release XRP/RLUSD payments. Runs locally from the @eamwhite1/agenttrust-sdk npm package.
mcp-hd-wallet
MCP server for HD wallet management, balance, and sync on EVM, UTXO, XRP via Crypto APIs. Runs locally from the @cryptoapis-io/mcp-hd-wallet npm package. Needs 1 environment variable to run.