mcpbeat Sign in

AgentPay MCP Server

answering

AgentPay is answering right now. Last checked 2 min ago. 102 installs a week from npm. Last commit 6 Sep 2026.

Agent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits.

Installs per day peak 33 · avg 13 · +23% w/w
a month agotoday
Uptime history 91 days of history · worst day 93%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
236 ms
Response time
average over 24h
102
Installs / week
npm and PyPI

What the code does

We read the source, 3 d ago · rules 995398eba69f

In the project's build, not in the package

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.

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Nothing serious here today

Today is the operative word: we check AgentPay every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add agentpay --transport http https://api.agentpay.so/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.agentpay.so/api/mcp
~/.codex/config.toml
[mcp_servers.agentpay]
url = "https://api.agentpay.so/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agentpay": {
      "url": "https://api.agentpay.so/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agentpay": {
      "type": "http",
      "url": "https://api.agentpay.so/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.agentpay.so/api/mcp streamable-http sign-in 41 ms 2 min ago

Alternatives to AgentPay

same job, measured the same way
XDC AI
by 0xbeny

Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.

answering
Clawvault MCP Server
by andrewszk

AI agent payment security - spending limits, whitelists, and human approval.

63 installs/wk local only
Bill Tracker
by jirawatp

Personal bill tracker: due dates, payments and spending reports. Sign in with Google or LINE.

answering
three.ws Agent Payments
by nirholas

Governed x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key.

83 installs/wk local only
Pink Agentic AI Payments
by pinkwallet

Pink Agentic AI Payments: AI agents pay within spending rules (budgets, caps, approval). Sandbox.

111 installs/wk answering
Clawallex MCP
by clawallex-tech

MCP Server for Clawallex payment API - Pay for anything with USDC virtual cards

51 installs/wk local only
HiveBank
by srotzin

USDC treasury vaults, streaming payments, and DeFi yield for AI agents

5 tools answering
Singularity Layer MCP
by ivaavimusic

MCP for Singularity Layer - discover listings, manage assets, run payment flows, and use agents

63 tools answering

AgentPay — questions

Answers built from our own checks of this server.

Why is there no tool list for AgentPay?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is AgentPay working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 236 ms. The bar chart above shows every period we have measured.
How do I connect AgentPay?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to AgentPay?
No API key is involved. AgentPay answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is AgentPay?
It answers our handshake in 236 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use AgentPay?
The npm package @agentpayxyz/mcp-server was installed 102 times in the last week. Week over week that is +23%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is AgentPay open source?
No, and the distinction matters: its licence is declared as BSL-1.1; AGPL-3.0 after 2029-01-01. That makes it source-available — you can read the code, but the terms are the author's own, not one of the recognised open-source licences. Read them before you build on it.