Finance · Local MCP server
agentpay
Enforced budgets for agents paying x402 APIs: the gateway holds the wallet, not the agent.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Hellotravisss/agentpay- Version
- 0.9.0
- Status
- Active
- Category
- finance
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- Hellotravisss (GitHub)
- Repository
- github.com/Hellotravisss/agentpay
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | agentpay-gateway | 0.9.0 | stdio |
How to connect agentpay
agentpay runs locally from a Node.js package published to the npm registry: agentpay-gateway version 0.9.0. 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 agentpay-gateway@0.9.0. It reads these environment variables: AGENTPAY_URL and AGENTPAY_API_KEY (secret); 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": {
"agentpay": {
"command": "npx",
"args": [
"-y",
"agentpay-gateway@0.9.0"
],
"env": {
"AGENTPAY_URL": "<value>",
"AGENTPAY_API_KEY": "<secret>"
}
}
}
}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 finance servers
| Server | Runs |
|---|---|
| AgentMart ProcurementProcure, compare, quote, budget, and execute web extraction or scraping across providers for agents. | Remote · HTTP |
| AgentmetalRent a Linux VPS from an AI agent: provision, SSH in, run commands. Pay USDC (x402) or card. | Local · stdio |
| AgentObserver - Check x402 Dependencies Before PayingCheck Exa, BlockRun, OneSource, Apify and other x402 dependencies before invoking or paying. | Remote · HTTP |
| AgentpayAI Agent payment protocol on CKB Fiber Network. Zero-gas micropayments with Hold Invoice escrow. | Local · stdio |
| AgentpayAI agent payments with human approval. Local-first, encrypted credentials, budget controls. | Local · stdio |
| AgentPayAgent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits. | Remote & Local · HTTP, stdio |
| AgentpaySpending controls for AI agents: per-agent budgets, vendor allowlists, full audit trail. | Local · stdio |
| AgentpayNon-custodial x402 payment MCP server for AI agents. Wallets and payments on 17 chains. | Local · stdio |