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/magpiecapital/magpie-x402Wrote 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/magpiecapital/magpie-x402/magpie-mcp)<a href="https://agentmods.dev/mcp/magpiecapital/magpie-x402/magpie-mcp"><img src="https://agentmods.dev/badge/mcp/magpiecapital/magpie-x402/magpie-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/magpiecapital/magpie-x402/magpie-mcp"><img src="https://agentmods.dev/badge/mcp/magpiecapital/magpie-x402/magpie-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
magpie-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 11d 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
{
"magpie-mcp": {
"command": "npx",
"args": [
"-y",
"@magpieloans/magpie-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.
- 11d ago First seen · 10 lines scan A f6f0ce136f1d
magpie-mcp is an MCP server published in the GitHub repository magpiecapital/magpie-x402 (7 stars, last pushed yesterday), 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
mcp-server
Concentrated liquidity on Uniswap/Aerodrome (rebalance, compound, leverage) or single-sided lending. Runs locally from the @arcadia-finance/mcp-server npm package. Needs 8 environment variables to run.
mcp-server
Agent payment infrastructure MCP server. Give AI agents autonomous payment capability — stablecoin transfers, currency swaps, agent wallets, and fiat operations on Hedera. Works with Claude, LangChain, CrewAI, AutoGPT. Runs locally from the @bananacrystal/mcp-server npm package.
datafood-mcp
DataFood: 16 data sources (crypto/DeFi/security/news/finance) via one MCP. Bundles save 92%. Remote server at toughlovesec.win.
mcp
Paid work for agents: claim verifier-checked jobs, submit, earn USDC. Some need no bond or funding. Remote server at api.averray.com.
mcp-moonpay
MCP server for MoonPay — fiat-to-crypto on/off-ramp, 100+ assets; Pix for Brazil onramp. Runs locally from the @codespar/mcp-moonpay npm package. Needs 6 environment variables to run.
mcp-coinbase-cdp
MCP server for Coinbase Developer Platform (CDP) — Trading, Wallets, Payments under one CDP key. Runs locally from the @codespar/mcp-coinbase-cdp npm package. Needs 2 environment variables to run.