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/ronaldanton/x402-shopWrote 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/ronaldanton/x402-shop/mcp-agentpay)<a href="https://agentmods.dev/mcp/ronaldanton/x402-shop/mcp-agentpay"><img src="https://agentmods.dev/badge/mcp/ronaldanton/x402-shop/mcp-agentpay/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/ronaldanton/x402-shop/mcp-agentpay"><img src="https://agentmods.dev/badge/mcp/ronaldanton/x402-shop/mcp-agentpay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentpay 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
{
"agentpay": {
"url": "https://agentpay.help/mcp",
"type": "streamable-http"
}
}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 d86c47eccb89
agentpay is an MCP server published in the GitHub repository ronaldanton/x402-shop (0 stars, last pushed 1mo ago), licensed Apache-2.0. 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-09-14.
Other mcp servers, from other repositories
scrape402
Pay-per-call agent tools via x402 (USDC on Base): chat, prices, funding, RNG. No account or keys. Remote server at x402.shizu.me.
deadchannel
Check an x402 endpoint before you pay it: verdict, risk score and what is wrong. $0.005 in USDC. Runs locally from the deadchannel-mcp npm package. Needs 2 environment variables to run.
hosaka
Company facts for AI agents: which vendors a company uses, proven from DNS. Paid in USDC. Runs locally from the hosaka-mcp npm package. Needs 2 environment variables to run.
ibm-x402-mcp
x402 pay-per-use MCP server for IBM Granite AI — chat, code, embeddings, analysis, and time-series forecasting. Pay USDC on Solana per call. No IBM Cloud account required. Runs locally from the @three-ws/ibm-x402-mcp npm package. Needs 9 environment variables to run.
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.
x402-commerce
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 8 environment variables to run.