Agentpay runs on your own machine — the client starts it, so there is no endpoint to ping. 461 installs a week from npm. Last commit 1 Nov 2026.
Non-custodial x402 payment MCP server for AI agents. Wallets and payments on 17 chains.
We read the source, 22 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
let drop = 0
while (drop < ring.length && ring[drop]!.timestamp < cutoff) drop++
if (drop > 0) {
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
excluded.push('.github/**', '.git/**', '**/.npmrc', '.gitmodules', '.gitattributes', '.husky/**');
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add agentpay -e 'AGENT_PRIVATE_KEY=<AGENT_PRIVATE_KEY>' -- npx -y agentpay-mcp
{
"mcpServers": {
"agentpay": {
"command": "npx",
"args": [
"-y",
"agentpay-mcp"
],
"env": {
"AGENT_PRIVATE_KEY": "<AGENT_PRIVATE_KEY>"
}
}
}
}
[mcp_servers.agentpay]
command = "npx"
args = ["-y", "agentpay-mcp"]
env = { AGENT_PRIVATE_KEY = "<AGENT_PRIVATE_KEY>" }
{
"mcpServers": {
"agentpay": {
"command": "npx",
"args": [
"-y",
"agentpay-mcp"
],
"env": {
"AGENT_PRIVATE_KEY": "<AGENT_PRIVATE_KEY>"
}
}
}
}
{
"servers": {
"agentpay": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agentpay-mcp"
],
"env": {
"AGENT_PRIVATE_KEY": "<AGENT_PRIVATE_KEY>"
}
}
}
}
Put your own value in place of
<AGENT_PRIVATE_KEY> (Private key for the agent wallet (hex string)).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
BASE_RPC_URL (Base RPC URL for on-chain operations).
Non-custodial x402 payment MCP server for AI agents. Wallets, payments, and commerce on 17 chains.
Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2.
Non-custodial HTTP-402 crypto payments for AI agents. 77-tool MCP server.
Non-custodial HTTP-402 crypto payments for AI agents. 79-tool MCP server.
x402 payment wrapper for AI Agents and MCP Servers. USDC settlements on Base L2.
Non-custodial x402 payments for AI agents. Sign locally, spend limits, Base network.
USDC wallets, payment links and x402 payments on Solana for AI agents.
Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.
Answers built from our own checks of this server.