
Agentpay Gateway Mcp
io.github.RumblingbPublished by GitHub account Rumblingbv1.0.0Updated Oct 27, 2026
Centralized API gateway routing to MCP servers with per-call billing
The publisher's own server: AgentPay — Pay-per-call AI Microservices
Overview
A self-hosted gateway that routes an assistant's tool calls to many backend MCP servers, with credit-based per-call billing behind one API key.
- What you can do
- Call tools across many backend servers through one gateway endpoint, covering search, weather, DNS, QR codes, screenshots, PDFs, crypto, legal and patent lookups
- Check credit balance, tier and daily usage, and get a Stripe checkout link when credits run out
- Proxy any backend tool by name with its own parameters plus the API key
- Run in a local demo mode without a database, or in a full mode with a Supabase credit ledger and Stripe billing
- When to use it
- Useful when you want a single MCP connection and one key instead of separate accounts for many small services, and you accept paying credits per call. Best suited to self-hosting the gateway rather than adding a hosted service.
- Requirements
- Python 3.10+ with the mcp, httpx and anyio packages, or Docker. The gateway runs as a separate HTTP server that must be started before the client connects, and clients connect with an X-API-Key header. Full mode needs SUPABASE_URL, SUPABASE_SERVICE_KEY, STRIPE_API_KEY and STRIPE_CHECKOUT_LINK.
Installation
In SourceWeft
- Open Agentpay Gateway Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
AgentPay Gateway MCP
One MCP installation gives your agent access to 42 backend servers — web search, legal analysis, domain intelligence, QR codes, email verification, SEC filings, patent lookup, and more — with per-call credit billing and one API key instead of 42.
What your agent can do
- Call any of the 90+ tools across 42 specialized backend servers through a single MCP endpoint — no separate accounts or API keys per service
- Pay per call using a credit system: most tools cost 1–3 credits, compute-heavy tools (contract analysis, SEO audit, legal contract generation) cost 5–8 credits
- Check remaining daily credits and account status at any time via
gateway_info - Get a Stripe checkout link to upgrade when credits are exhausted — the server returns the URL directly
- Run in demo mode locally (no database) or full mode with Supabase-backed credit ledger and Stripe billing
- Deploy via Docker with environment variables for a production-ready self-hosted gateway
Installation
Requires: Python 3.10+, mcp, httpx, anyio packages.
The gateway runs as an HTTP server (not stdio). It must be started separately before connecting your MCP client.
Claude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Cursor — add to .cursor/mcp.json in your project root:
Docker:
Tool Reference
Credit costs by category
Backend Server Registry (42 servers)
Pricing
Credits reset daily. When credits are exhausted, gateway_upsell returns a Stripe checkout URL.
License
MIT — AgentPay Labs. Source: github.com/Rumblingb/agentpay-gateway-mcp
Source: README.md at commit efd697a
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Agentpay integrations
AgentPay — Pay-per-call AI Microservices
help.agentpayOfficial publisher
AgentPay offers 34 pay-per-call AI and data microservices over x402, settled in USDC on Base, with no API keys required.

AgentPay Doc Tools
Published by GitHub account noah-silver
Remote MCP server offering paid per-call document and web utilities: PDF-to-text, RSS/Atom/JSON feed parsing, and sitemap URL listing.

AgentPay Domain & Network Lookup
Published by GitHub account noah-silver
Remote MCP server for paid DNS, WHOIS/RDAP, IP ownership and combined domain reports, billed per call in USDC or prepaid credits.

AgentPay Web Extract
Published by GitHub account noah-silver
A remote pay-per-call MCP server that fetches a web page and returns clean markdown, metadata and links for an assistant.

AgentPay (all tools)
Published by GitHub account noah-silver
Remote pay-per-call MCP server offering web page extraction, DNS/WHOIS/IP lookups, and PDF, feed and sitemap tools, billed in USDC or prepaid credits.