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/true402/mcp-serverWrote 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/true402/mcp-server/mcp-server)<a href="https://agentmods.dev/mcp/true402/mcp-server/mcp-server"><img src="https://agentmods.dev/badge/mcp/true402/mcp-server/mcp-server/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/true402/mcp-server/mcp-server"><img src="https://agentmods.dev/badge/mcp/true402/mcp-server/mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-server 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
{
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@true402.dev/mcp-server"
],
"env": {
"WALLET_PRIVATE_KEY": "",
"SERVER_URL": "",
"MAX_PAYMENT_USDC": ""
}
}
}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 · 14 lines scan A e348e31fb19d
mcp-server is an MCP server published in the GitHub repository true402/mcp-server (0 stars, last pushed 2d 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
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.
pulsefeed-x402
Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores. Runs locally from the pulsefeed-x402-mcp npm package.
x402-bazaar-mcp
Check, then act, on Base and NEAR: token-safety gates, then swaps at the best price — over x402. Runs locally from the x402-bazaar-mcp npm package. Needs 3 environment variables to run.
robyn
Gasless cross-chain for AI agents: 25 nodes incl. Solana & native Bitcoin. One signature, no gas. Runs locally from the anygas-mcp npm package. Needs 2 environment variables to run.
warden402-mcp
Pre-execution safety for AI agents on Base. Guard a token, tx or address: block/review/clear. Runs locally from the warden402-mcp npm package. Needs 1 environment variable to run.
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.