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/flat-cash/flatcash-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/flat-cash/flatcash-mcp/flatcash)<a href="https://agentmods.dev/mcp/flat-cash/flatcash-mcp/flatcash"><img src="https://agentmods.dev/badge/mcp/flat-cash/flatcash-mcp/flatcash.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
flatcash 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 7d 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
{ "flatcash": { "command": "npx", "args": [ "-y", "flatcash-mcp" ], "env": {} } }
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.
- 7d ago First seen · 10 lines scan A f5667429ddb5
flatcash is an MCP server published in the GitHub repository flat-cash/flatcash-mcp (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
coingecko-mcp-server
Crypto market data via CoinGecko — prices, markets, history, trending, and deep coin metadata. Runs locally from the @cyanheads/coingecko-mcp-server npm package. Needs 2 environment variables to run.
verdictswarm
Every tool has an answer — your agent needs a decision. MCP server for the VerdictSwarm pre-trade check: a machine-readable avoid/caution/clear before your agent trades, plus intended-size exit feasibility and holder-cluster attribution on Solana. Runs locally from the verdictswarm-mcp Python package. Needs 3…
verdictswarm-mcp
Every tool has an answer — your agent needs a decision. MCP server for the VerdictSwarm pre-trade check: a machine-readable avoid/caution/clear before your agent trades, plus intended-size exit feasibility and holder-cluster attribution on Solana. Runs locally from the verdictswarm-mcp Python package. Needs 1…
defi-vaults
Search 700+ DeFi vaults, compare risk scores, analyze protocols. No API key needed. Remote server at mcp.philidor.io.
rug-munch-mcp
MCP server for Rug Munch Intelligence — 19 tools for crypto token risk analysis, rug pull detection, and AI forensics. Runs locally from the rug-munch-mcp Python package. Needs 2 environment variables to run.
perp-cli
Multi-DEX Perpetual Futures CLI - Pacifica, Hyperliquid, Lighter, Aster. Runs locally from the perp-cli npm package.