Agentpay

Non-custodial x402 payment MCP server for AI agents. Wallets and payments on 17 chains.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "agentpay-7": {
      "command": "npx",
      "args": [
        "-y",
        "agentpay-7"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

AgentPay MCP

AgentPay MCP is a stdio Model Context Protocol server for x402 payments and wallet operations. It exposes Agent Wallet SDK functions as MCP tools and loads a caller-controlled signing key from the local process environment.

The current npm package is agentpay-mcp v4.1.17.

Start without funds

Check the installed command without loading wallet credentials:

Terminal

npx -y agentpay-mcp --version
npx -y agentpay-mcp --help

Use the AgentPay Wallet Starter for a no-funds verification of allowed, approval-required, and blocked policy outcomes.

MCP client configuration

Wallet tools read the following environment variables:

Variable	Required for wallet tools	Meaning
`AGENT_PRIVATE_KEY`	Yes	Local hot-wallet signing key
`AGENT_WALLET_ADDRESS`	Yes	Deployed `AgentAccountV2` address
`CHAIN_ID`	No	`8453` or `84532`; defaults to Base mainnet
`RPC_URL`	No	Caller-selected Base RPC endpoint
`FACTORY_ADDRESS`	For deployment	Wallet factory address
`NFT_CONTRACT_ADDRESS`	For deployment	Token contract bound to a wallet
`SESSION_TTL_SECONDS`	No	Local session lifetime in seconds

Example MCP configuration:

config.json

{
  "mcpServers": {
    "agentpay": {
      "command": "npx",
      "args": ["-y", "agentpay-mcp"],
      "env": {
        "AGENT_PRIVATE_KEY": "<secret-reference-or-local-key>",
        "AGENT_WALLET_ADDRESS": "0x<deployed-wallet-address>",
        "CHAIN_ID": "84532"
      }
    }
  }
}

Do not commit a real signing key. Use the client or operating system's secret mechanism where one exists. Start on Base Sepolia before using Base mainnet.

Tool groups

The tool registry in src/index.ts exposes these groups:

Group	Examples
Wallet	`deploy_wallet`, `get_wallet_info`, `queue_approval`
Payments	`send_payment`, `x402_pay`, x402 session tools
Policy	`set_spend_policy`, `check_budget`, OTel budget tools
Tokens	Lookup, custom-token registration, balances, and transfers
Execution	Swap, USDC bridge, and mutual-stake escrow
Trust	ERC-8004 identity, reputation, and UAID verification
History	`get_transaction_history` for wallet contract events

Tool schemas and handlers live under src/tools/.

Security boundaries

These boundaries matter more than the feature list:

The server reads AGENT_PRIVATE_KEY into its local Node.js process and uses viem for signing. Protect the process, environment, and MCP client config.
set_spend_policy stores policy in the MCP server process. The same agent can call that tool again, and a process restart clears its rolling state.
Every current value-moving handler calls the in-process policy check, but this is still application-level enforcement.
On-chain limits exist only when the wallet owner configures them directly on AgentAccountV2. set_spend_policy does not write those contract limits.
An over-limit transaction is a human gate only when the owner key is kept separate from the agent key.
get_transaction_history reads on-chain wallet events. It is not an MCP request log and does not record rejected pre-chain attempts or read-only calls.
Runtime wallet configuration currently supports Base mainnet and Base Sepolia. Unsupported chain IDs fail closed in src/utils/client.ts.
Swap, bridge, escrow, and payment tools can move funds and consume gas. Test with bounded values and independent wallet limits.

Read docs/security-posture.md for the detailed control map and known limitations.

Technical proof index

The repository keeps deeper interoperability and buyer-safety evidence in versioned documents:

docs/agentpay-buyer-flow-parity.md covers typed payment errors and buyer flow behavior.
docs/paid-mcp-gateway-hardening.md covers default-deny controls and quota envelopes.
docs/agentpay-five-tool-parity-proof.md records the five-tool parity check.
docs/agentpay-escrow-reputation-boundary.md defines the escrow and reputation boundary.
docs/paid-mcp-proxy-discovery-readiness.md records discovery readiness evidence.
docs/x402-chain-neutral-gateway-profile.md defines the packaged chain-neutral profile.
docs/x402-dynamic-paid-mcp-manifest-drift.md documents checks for stale paid-tool metadata.
docs/mcp-registry-listing-proof.md and llms.txt expose directory metadata.
docs/smithery-paid-mcp-installation.md and examples/smithery-paid-mcp-installation document the packaged Smithery path without asserting a live listing.
docs/paid-provider-health-proof.md defines provider-health evidence.
docs/hosted-x402-proxy-verification.md defines hosted-proxy preflight checks.
docs/x402-native-vs-stripe-proxy.md separates local spend control from hosted proxy billing.
docs/dependency-pin-policy.md defines the release gate for payment-critical packages.

AgentPay pins viem exactly at 2.56.0.

The directory comparison was captured against agentpay-mcp@4.1.9; the package version at the top of this README is the current release.

Verify a clean checkout

Terminal

npm ci
npm run build
npm run typecheck
npm test
npm run lint
npm run security
npm run smoke:clean-install

The CI workflow is separate from scheduled daily review and repair workflows. A scheduled-review failure is not a product-test result, and a repair success does not replace CI.

Related repositories

Agent Wallet SDK provides the wallet and policy library used by this server.
AgentPay Wallet Starter provides the combined no-funds onboarding path.
NVIDIA NeMo Agent Toolkit Examples PR 17 is an independently merged integration example.

Support and disclosure

File product bugs through the GitHub issue queue.
Report security issues through SECURITY.md.
Contribution rules live in CONTRIBUTING.md.

License

MIT. See LICENSE.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Finance & Fintech View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Agentpay

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "agentpay": { "command": "npx", "args": ["-y", "agentpay"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/agentpay-7?style=directory)](https://allmcps.com/mcp/agentpay-7)

HTML Embed

<a href="https://allmcps.com/mcp/agentpay-7"><img src="https://allmcps.com/api/badge/agentpay-7?style=directory" alt="Agentpay on AllMCPs" /></a>

Technical Specs & Signals

CategoryFinance & Fintech

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

AllMCPs Server

The official MCP server for AllMCPs.com - submit and manage tools directly from your AI. The open directory for MCP servers. Connect Claude, Cursor, Windsurf, and AI agents to databases, tools, files, and APIs. Explore 10,000+ servers. AllMCPs is the premier, open directory for discovering, evaluating, and installing Model Context Protocol (MCP) servers to equip AI agents and LLMs with real-world superpowers.

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💰 Finance & Fintech →Best MCP servers for Finance & Fintech →Alternatives to Agentpay →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

AgentPay MCP

The current npm package is agentpay-mcp v4.1.17.

Start without funds

Check the installed command without loading wallet credentials:

Terminal

npx -y agentpay-mcp --version
npx -y agentpay-mcp --help

Use the AgentPay Wallet Starter for a no-funds verification of allowed, approval-required, and blocked policy outcomes.

MCP client configuration

Wallet tools read the following environment variables:

Variable	Required for wallet tools	Meaning
`AGENT_PRIVATE_KEY`	Yes	Local hot-wallet signing key
`AGENT_WALLET_ADDRESS`	Yes	Deployed `AgentAccountV2` address
`CHAIN_ID`	No	`8453` or `84532`; defaults to Base mainnet
`RPC_URL`	No	Caller-selected Base RPC endpoint
`FACTORY_ADDRESS`	For deployment	Wallet factory address
`NFT_CONTRACT_ADDRESS`	For deployment	Token contract bound to a wallet
`SESSION_TTL_SECONDS`	No	Local session lifetime in seconds

Example MCP configuration:

config.json

{
  "mcpServers": {
    "agentpay": {
      "command": "npx",
      "args": ["-y", "agentpay-mcp"],
      "env": {
        "AGENT_PRIVATE_KEY": "<secret-reference-or-local-key>",
        "AGENT_WALLET_ADDRESS": "0x<deployed-wallet-address>",
        "CHAIN_ID": "84532"
      }
    }
  }
}

Do not commit a real signing key. Use the client or operating system's secret mechanism where one exists. Start on Base Sepolia before using Base mainnet.

Tool groups

The tool registry in src/index.ts exposes these groups:

Group	Examples
Wallet	`deploy_wallet`, `get_wallet_info`, `queue_approval`
Payments	`send_payment`, `x402_pay`, x402 session tools
Policy	`set_spend_policy`, `check_budget`, OTel budget tools
Tokens	Lookup, custom-token registration, balances, and transfers
Execution	Swap, USDC bridge, and mutual-stake escrow
Trust	ERC-8004 identity, reputation, and UAID verification
History	`get_transaction_history` for wallet contract events

Tool schemas and handlers live under src/tools/.

Security boundaries

These boundaries matter more than the feature list:

The server reads AGENT_PRIVATE_KEY into its local Node.js process and uses viem for signing. Protect the process, environment, and MCP client config.
set_spend_policy stores policy in the MCP server process. The same agent can call that tool again, and a process restart clears its rolling state.
Every current value-moving handler calls the in-process policy check, but this is still application-level enforcement.
On-chain limits exist only when the wallet owner configures them directly on AgentAccountV2. set_spend_policy does not write those contract limits.
An over-limit transaction is a human gate only when the owner key is kept separate from the agent key.
get_transaction_history reads on-chain wallet events. It is not an MCP request log and does not record rejected pre-chain attempts or read-only calls.
Runtime wallet configuration currently supports Base mainnet and Base Sepolia. Unsupported chain IDs fail closed in src/utils/client.ts.
Swap, bridge, escrow, and payment tools can move funds and consume gas. Test with bounded values and independent wallet limits.

Read docs/security-posture.md for the detailed control map and known limitations.

Technical proof index

The repository keeps deeper interoperability and buyer-safety evidence in versioned documents:

docs/agentpay-buyer-flow-parity.md covers typed payment errors and buyer flow behavior.
docs/paid-mcp-gateway-hardening.md covers default-deny controls and quota envelopes.
docs/agentpay-five-tool-parity-proof.md records the five-tool parity check.
docs/agentpay-escrow-reputation-boundary.md defines the escrow and reputation boundary.
docs/paid-mcp-proxy-discovery-readiness.md records discovery readiness evidence.
docs/x402-chain-neutral-gateway-profile.md defines the packaged chain-neutral profile.
docs/x402-dynamic-paid-mcp-manifest-drift.md documents checks for stale paid-tool metadata.
docs/mcp-registry-listing-proof.md and llms.txt expose directory metadata.
docs/smithery-paid-mcp-installation.md and examples/smithery-paid-mcp-installation document the packaged Smithery path without asserting a live listing.
docs/paid-provider-health-proof.md defines provider-health evidence.
docs/hosted-x402-proxy-verification.md defines hosted-proxy preflight checks.
docs/x402-native-vs-stripe-proxy.md separates local spend control from hosted proxy billing.
docs/dependency-pin-policy.md defines the release gate for payment-critical packages.

AgentPay pins viem exactly at 2.56.0.

The directory comparison was captured against agentpay-mcp@4.1.9; the package version at the top of this README is the current release.

Verify a clean checkout

Terminal

npm ci
npm run build
npm run typecheck
npm test
npm run lint
npm run security
npm run smoke:clean-install

The CI workflow is separate from scheduled daily review and repair workflows. A scheduled-review failure is not a product-test result, and a repair success does not replace CI.

Related repositories

Agent Wallet SDK provides the wallet and policy library used by this server.
AgentPay Wallet Starter provides the combined no-funds onboarding path.
NVIDIA NeMo Agent Toolkit Examples PR 17 is an independently merged integration example.

Support and disclosure

File product bugs through the GitHub issue queue.
Report security issues through SECURITY.md.
Contribution rules live in CONTRIBUTING.md.

License

MIT. See LICENSE.