Finance · Local MCP server
Agent Pay
Payment gateway for AI agents with tool discovery, provisioning, metering, and reliability tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.joepangallo/agent-pay- Version
- 1.1.2
- Status
- Active
- Category
- finance
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-03-23
- Updated
- 2026-03-23
- Publisher
- joepangallo (GitHub) · 8 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/joepangallo) · how
- Repository
- github.com/joepangallo/agent-pay
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | mcp-server-agentpay | 1.1.2 | stdio |
How to connect Agent Pay
Agent Pay runs locally from a Node.js package published to the npm registry: mcp-server-agentpay version 1.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y mcp-server-agentpay@1.1.2. It reads these environment variables: AGENTPAY_GATEWAY_KEY (required, secret), AGENTPAY_ADMIN_KEY (secret) and AGENTPAY_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"agent-pay": {
"command": "npx",
"args": [
"-y",
"mcp-server-agentpay@1.1.2"
],
"env": {
"AGENTPAY_GATEWAY_KEY": "<secret>",
"AGENTPAY_ADMIN_KEY": "<secret>",
"AGENTPAY_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from joepangallo (GitHub)
| Server | Runs |
|---|---|
| Cloud AgentAI software engineer - writes code, opens PRs, reviews code, generates tests, and more. | Local · stdio |
| MCP Audit ServerThin MCP and CLI proxy for AI agent and MCP security auditing via a hosted backend. | Local · stdio |
| MCP Server Agent AnalyticsTrack AI agent fleet performance, costs, anomalies, and trends. | Local · stdio |
| MCP Server IndexforgeSubmit URLs to Google and Bing for indexing, scan sitemaps, check index status. | Local · stdio |
| MCP Server Research SignalsScored trend intelligence from HN, Reddit, ArXiv, and GitHub. | Local · stdio |
| MCP Server Security AuditScan websites for security vulnerabilities, headers, TLS, and email security. | Local · stdio |
| Web Recon AgentOwned-target web security assessment MCP server for authenticated, high-friction apps. | Local · stdio |
More finance servers
| Server | Runs |
|---|---|
| Agent HandoffPass messages between AI agents with cleaning, metadata enrichment, and metered billing. | Remote · HTTPLive check: ✓ handshake |
| Agent Lead GenerationLeads from agents: hops attributed with a per-hop utm_id from discovery to trial to invoice. | Remote · HTTPLive check: ✓ handshake |
| Agent Margin Router38 x402 pay-per-call tools for AI agents (USDC/USDT on Base): web, crypto, on-chain, geo, packages. | Remote · HTTPLive check: ✓ handshake |
| Agent MeteringUsage metering + SLA accounting for agent services (the meter behind x402 micropayments). | Remote · HTTPLive check: ✓ handshake |
| Agent PaymentStripe-style USDC billing for any API. 8 free demo services no signup. Non-custodial. | Local · stdio |
| Agent Payment MCPSecure USDC payments for AI agents on Base blockchain with budget controls and instant settlement. | Local · stdio |
| Agent Payment MCPSecure MCP router providing access to AgentPMT's pay-per-use AI tools marketplace. | Local · stdio |
| Agent Reserve Protocol Authorization FirewallAdvisory policy preflight for AI-agent spend requests; never executes payments or accesses wallets. | Remote · HTTPLive check: ✓ handshake |