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/kota1026/quantum-shieldWrote 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/kota1026/quantum-shield/cryptodata-mcp)<a href="https://agentmods.dev/mcp/kota1026/quantum-shield/cryptodata-mcp"><img src="https://agentmods.dev/badge/mcp/kota1026/quantum-shield/cryptodata-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cryptodata-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 6d 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
{ "cryptodata-mcp": { "command": "npx", "args": [ "-y", "cryptodata-mcp" ], "env": {} } }
What else
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 6d ago First seen · 10 lines scan A c20f86d7ed21
cryptodata-mcp is an MCP server published in the GitHub repository kota1026/quantum-shield (0 stars, last pushed 9d 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
bvcc-agent-wallet
Non-custodial BVCC Agent Wallet on-chain for AI agents: balances, transfers, approvals, swaps. Runs locally from the @bvcc/agent-mcp npm package. Needs 6 environment variables to run.
base-l2-agent-kit
MCP server providing Base L2 DeFi tools for AI agents. Runs locally from the base-l2-agent-kit Python package.
perp-cli
Multi-DEX Perpetual Futures CLI - Pacifica, Hyperliquid, Lighter, Aster. Runs locally from the perp-cli npm package.
waiaas
WAIaaS MCP server - Model Context Protocol integration for AI agents. Runs locally from the @waiaas/mcp npm package. Needs 2 environment variables to run.
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.
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.