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/zeam-labs/x402-mcp-bridgeWrote 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/zeam-labs/x402-mcp-bridge/x402-mcp-bridge)<a href="https://agentmods.dev/mcp/zeam-labs/x402-mcp-bridge/x402-mcp-bridge"><img src="https://agentmods.dev/badge/mcp/zeam-labs/x402-mcp-bridge/x402-mcp-bridge/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/zeam-labs/x402-mcp-bridge/x402-mcp-bridge"><img src="https://agentmods.dev/badge/mcp/zeam-labs/x402-mcp-bridge/x402-mcp-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
x402-mcp-bridge 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
{ "x402-mcp-bridge": { "command": "npx", "args": [ "-y", "@zeam-labs/x402-mcp-bridge" ] } }
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 · 9 lines scan A c1d9f89e78cc
x402-mcp-bridge is an MCP server published in the GitHub repository zeam-labs/x402-mcp-bridge (0 stars, last pushed 19d 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
agentfeed-algo
Cross-exchange liquidation tape, paid per call in USDC on Algorand. Free catalog, no key needed. Runs locally from the @seekdaseek/agentfeed-algo npm package. Needs 3 environment variables to run.
xenarch-mcp
Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2. Runs locally from the @xenarch/agent-mcp npm package. Needs 4 environment variables to run.
onchain-agent-wallets
Give an AI agent a Solana spending allowance instead of your key. Chain-enforced cap, x402. Runs locally from the @three-ws/onchain-agent-wallets npm package. Needs 5 environment variables to run.
agenticpay
Real MCP server (stdio + @modelcontextprotocol/sdk) that exposes x402-paywalled HTTP endpoints as MCP tools. Drop into Claude Desktop, Cursor, or any MCP client. Runs locally from the @agenticpay/mcp-bridge npm package. Needs 6 environment variables to run.
hermes-plant
Preflight, approve, and prove consequential agent actions with signed evidence and x402 tools. Remote server at mcp.hermesplant.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.