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/Rotwang9000/flashbank-netWrote 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/rotwang9000/flashbank-net/flashbank)<a href="https://agentmods.dev/mcp/rotwang9000/flashbank-net/flashbank"><img src="https://agentmods.dev/badge/mcp/rotwang9000/flashbank-net/flashbank/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/rotwang9000/flashbank-net/flashbank"><img src="https://agentmods.dev/badge/mcp/rotwang9000/flashbank-net/flashbank.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
flashbank 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 8d 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
{
"flashbank": {
"command": "npx",
"args": [
"-y",
"@flashbank/mcp"
],
"env": {
"FLASHBANK_MCP_PRIVATE_KEY": "",
"FLASHBANK_MCP_ALLOW_MAINNET": "",
"FLASHBANK_MCP_RPC_SEPOLIA": ""
}
}
}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.
- 8d ago First seen · 14 lines scan A 24059b76282d
flashbank is an MCP server published in the GitHub repository Rotwang9000/flashbank-net (0 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
aegis-defi
A safety layer for autonomous DeFi agents - MCP server + smart contracts that simulate, scan, and protect on-chain transactions before execution. Runs locally from the aegis-defi npm package.
pumpclaw
Free token launcher on Base. Deploy ERC-20 tokens via Uniswap V4 with 80% creator fees. Runs locally from the pumpclaw-mcp npm package. Needs 2 environment variables to run.
base-wallet-toolkit
MCP server for Base wallet interactions: balances, gas, tokens, allowances, ENS. Runs locally from the base-wallet-toolkit-mcp npm package. Needs 1 environment variable to run.
perp-cli
Multi-DEX Perpetual Futures CLI - Pacifica, Hyperliquid, Lighter, Aster. Runs locally from the perp-cli npm package.
crypto-quant-signal-mcp
Quant trading signals, funding rate arb scanning, and market regime detection for crypto perps. Runs locally from the crypto-quant-signal-mcp 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.