Finance · Local MCP server
Agentpay
Non-custodial x402 payment MCP server for AI agents. Wallets and payments on 17 chains.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.up2itnow0822/agentpay- Version
- 3.1.0
- Status
- Active
- Category
- finance
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-03-21
- Updated
- 2026-03-21
- Publisher
- up2itnow0822 (GitHub) · 2 servers with pages here
- Repository
- github.com/up2itnow0822/agentpay-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | agentpay-mcp | 3.1.0 | stdio |
How to connect Agentpay
Agentpay runs locally from a Node.js package published to the npm registry: agentpay-mcp version 3.1.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-mcp@3.1.0. It reads these environment variables: AGENT_PRIVATE_KEY (required, secret) and BASE_RPC_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": {
"agentpay": {
"command": "npx",
"args": [
"-y",
"agentpay-mcp@3.1.0"
],
"env": {
"AGENT_PRIVATE_KEY": "<secret>",
"BASE_RPC_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 up2itnow0822 (GitHub)
| Server | Runs |
|---|---|
| ClawpayNon-custodial x402 payment MCP server for AI agents. Wallets, payments, and commerce on 17 chains. | Local · stdio |
More finance servers
| Server | Runs |
|---|---|
| agentpayEnforced budgets for agents paying x402 APIs: the gateway holds the wallet, not the agent. | 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 |
| AgentPayX402 micropayments MCP: Xiaohongshu notes and paid APIs settled in USDC on Base. | Remote & Local · HTTP, stdio |
| AgentPayRU merchant catalog for AI agents: live price, stock, choices and controlled checkout. Not x402. | Remote · HTTP |
| AgentPay — Pay-per-call AI Microservices34 pay-per-call AI microservices via x402, USDC on Base, no API keys. | Remote · HTTP |
| AgentPay — trust routing + spend caps for x402 agentsBuyer-side trust oracle + capped sessions for x402 agents: verified_route, receipts, 17 free tools. | Remote & Local · HTTP, stdio |