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/geoacpfilho/paygate-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/geoacpfilho/paygate-mcp/paygate-monetize-monetization-x402)<a href="https://agentmods.dev/mcp/geoacpfilho/paygate-mcp/paygate-monetize-monetization-x402"><img src="https://agentmods.dev/badge/mcp/geoacpfilho/paygate-mcp/paygate-monetize-monetization-x402/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/geoacpfilho/paygate-mcp/paygate-monetize-monetization-x402"><img src="https://agentmods.dev/badge/mcp/geoacpfilho/paygate-mcp/paygate-monetize-monetization-x402.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
paygate-monetize-monetization-x402 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 12d 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
{
"paygate-monetize-monetization-x402": {
"url": "https://paygate-mcp.rendercriativo.workers.dev/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.
- 12d ago First seen · 6 lines scan A f2b10dfb64b0
paygate-monetize-monetization-x402 is an MCP server published in the GitHub repository geoacpfilho/paygate-mcp (0 stars, last pushed 29d 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
loyal-spark
Onchain loyalty MCP on Base: programs, mint, rewards, vouchers for AI agents. Remote server at api.loyalspark.online.
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.
x402-commerce-solana
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 7 environment variables to run.
x402-commerce-sandbox
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 4 environment variables to run.
payanagent
Give your agent purchasing power — discover and buy 24,000+ live x402 services with USDC on Base. MCP server for the PayanAgent marketplace: buy, offer, request, fulfill. Runs locally from the @payanagent/mcp npm package.
inventpay-mcp
InventPay MCP Server - Give AI agents the ability to manage crypto payments, stores, products, and orders. Runs locally from the inventpay-mcp npm package.