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/zekebuilds-lab/mcp-pay-gateWrote 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/zekebuilds-lab/mcp-pay-gate/mcp-pay-gate)<a href="https://agentmods.dev/mcp/zekebuilds-lab/mcp-pay-gate/mcp-pay-gate"><img src="https://agentmods.dev/badge/mcp/zekebuilds-lab/mcp-pay-gate/mcp-pay-gate/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/zekebuilds-lab/mcp-pay-gate/mcp-pay-gate"><img src="https://agentmods.dev/badge/mcp/zekebuilds-lab/mcp-pay-gate/mcp-pay-gate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-pay-gate 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 10d 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-pay-gate": {
"command": "npx",
"args": [
"-y",
"@powforge/mcp-pay-gate"
],
"env": {
"POW_GATE_URL": "https://gate.powforge.dev"
}
}
}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.
- 10d ago First seen · 12 lines scan A e925e6e0ac77
mcp-pay-gate is an MCP server published in the GitHub repository zekebuilds-lab/mcp-pay-gate (0 stars, last pushed 4mo 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…
saturnzap
CLI-first, non-custodial Lightning Network wallet for autonomous AI agents. Runs locally from the saturnzap Python package. Needs 2 environment variables to run.
arsenal-decision-engine
Rnet LP risk evaluator for DeFAI agents. IL + Breakeven Corridor O(1). L402 Lightning paywall. Remote server at api.arsenal-quant.com.
lightning-wallet-mcp
Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support. Runs locally from the lightning-wallet-mcp npm package.
base-defi
Base chain DeFi yields — Aerodrome, Moonwell, APY, TVL, risk scores. x402. Remote server at base-defi.api.klymax402.com.
defi-yields
Best DeFi yields by token — APY, TVL, risk, protocol. DeFiLlama-powered. x402. Remote server at defi-yields.api.klymax402.com.