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.
npx agentmods add mcp/up2itnow0822/agentpay-mcp/agentpaygit clone --depth 1 https://github.com/up2itnow0822/agentpay-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/up2itnow0822/agentpay-mcp/agentpay)<a href="https://agentmods.dev/mcp/up2itnow0822/agentpay-mcp/agentpay"><img src="https://agentmods.dev/badge/mcp/up2itnow0822/agentpay-mcp/agentpay.svg" alt="Measured on agentmods" 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 5d 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": {
"command": "npx",
"args": [
"-y",
"agentpay-mcp"
],
"env": {
"AGENT_PRIVATE_KEY": "",
"BASE_RPC_URL": ""
}
}
}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.
- 5d ago First seen · 13 lines scan A 0cad28ddab1a
agentpay is an MCP server published in the GitHub repository up2itnow0822/agentpay-mcp (5 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
x402-list-mcp
MCP server for x402-list: discover x402 payment services, on-chain-verified facilitator settlement volume, server-ranked recommendations, and paid on-demand assessments (x402 pass-through, never holds keys). Thin wrapper over the public x402-list API. Runs locally from the x402-list-mcp npm package. Needs 2…
buyforme-mcp
BuyForMe: pay any x402 URL (USD or EUR) with ArisPay delegated custody. Alias of payagent-mcp. Runs locally from the buyforme-mcp npm package. Needs 2 environment variables to run.
hiveclear
Multi-agent settlement and clearing with validator consensus. Remote server at hiveclear.onrender.com.
yolfi-agent
Let AI agents add Yolfi crypto checkout, paylinks, webhooks, and status checks. Runs locally from the @yolfi/agent npm package. Needs 2 environment variables to run.
nano-pay
Feeless x402 micropayments for AI agents — self-custodied XNO wallet, pay-per-call client, merchant server with railHint, faucet, and MCP server. Runs locally from the feeless402 Python package.
q402-mcp
Q402 - gasless payments, yield, escrow, bridge & NAV triggers on 12 EVM chains. Sandbox-default. Runs locally from the @quackai/q402-mcp npm package. Needs 12 environment variables to run.