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/agishub/agishub-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/agishub/agishub-mcp/crypto-prices)<a href="https://agentmods.dev/mcp/agishub/agishub-mcp/crypto-prices"><img src="https://agentmods.dev/badge/mcp/agishub/agishub-mcp/crypto-prices/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/agishub/agishub-mcp/crypto-prices"><img src="https://agentmods.dev/badge/mcp/agishub/agishub-mcp/crypto-prices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
crypto-prices 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
{
"crypto-prices": {
"url": "https://api.agishub.com/mcp/crypto",
"type": "streamable-http"
}
}What else server.json configures
This page is one entry in a file that holds 7. 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.
- 1mo ago First seen · 6 lines scan A 9ab9a84ccd83
crypto-prices is an MCP server published in the GitHub repository agishub/agishub-mcp (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
x402-seller
Rug-check & launch radar for trading agents: composite honeypot score, EVM+Solana, keyless x402. Remote server at x402-seller-m8nx.onrender.com.
whale-data-mcp
Signed settled outcomes (Polymarket, sports, Kalshi) + whale signals as agent tools, paid via x402. Runs locally from the @predge/whale-data-mcp npm package. Needs 7 environment variables to run.
frantic-mcp
A public bounty board where AI agents do paid work. USDC on Base, paid on accepted delivery. Runs locally from the frantic-mcp npm package.
agentservices
52 paid x402 API endpoints for AI agents — crypto, data, DeFi, market intelligence. Remote server at agentservices.to.
base-onchain-wallet-tokens
Read-only on-chain intelligence for AI agents on Base: balances, tokens, gas, tx status. Remote server at base.datakoot.com.
mainstreet
Reputation oracle for AI agents on Base: SAFE/CAUTION/BLOCK + 0-100 score before you pay. x402+MCP. Remote server at avisradar-production.up.railway.app.