mcpbeat Sign in

agpay MCP Server

answering

agpay is answering right now. Last checked 2 min ago. It exposes 6 tools.

Payments held between two agents: buyer pays, seller delivers, buyer confirms. Pay per call.

Uptime history 5 days of history · worst day 99%
5 days agonow
100.0%
Uptime 24h
92 of 92 checks
6
Tools
read from the server
119 ms
Response time
average over 24h
open, no key
Access
streamable-http

agpay missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

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 agpay --transport http https://agpay.shveik.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agpay": {
      "url": "https://agpay.shveik.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agpay]
url = "https://agpay.shveik.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agpay": {
      "url": "https://agpay.shveik.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agpay": {
      "url": "https://agpay.shveik.dev/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

deal
create_deal
Open an escrow deal with a seller agent. Pay in stablecoins with x402 like the HTTP route: call without a payment to get the quote, then again with the signed payment in _meta. The answer is the receipt; act only on state funded. Choose the buyer secret yourself and send only its SHA-256 hash as secret_hash; keep the secret to confirm or dispute the deal.
get_deal
Get the status of a deal: its state, amounts, deadlines and outcome. Free; needs only the deal id. Act only on state funded.
confirm
confirm_deal
Confirm a deal as its buyer: the seller is paid now and the deal closes. Free; needs the deal id and the buyer secret. Confirming is final.
deals
list_deals
List the deals of an address, as seller or as buyer, newest first. Free; give exactly one of seller or buyer, an address. Everything except statements is visible to anyone who knows the address.
feedback
feedback
Free. Tell the people who run this service what worked, what failed or what you miss: a bug, an idea or a thanks. A person reads it. No payment, no account; limited to a few messages an hour.
statement
add_statement
Add a statement to a deal as its buyer, up to 2000 characters. Free; needs the deal id, the buyer secret and the text. Statements are visible to the operator only.

Endpoints

URLTransportStateLatencyChecked
https://agpay.shveik.dev/mcp streamable-http answering 127 ms 2 min ago

Alternatives to agpay

same job, measured the same way
x402 Atlas
by ausrine-labs

The x402 agent market on Base: sellers, prices, on-chain payments, operators, buyers. Dated.

local only
A
agents.u.cash
by udotcash

Non-custodial 402 payments for agents. 88-tool stdio seller MCP + hosted keyless buyer twin.

local only
MCP Zoop
by codespar

MCP server for Zoop — marketplace payments, splits, sellers, buyers, transfers

33 installs/wk local only
TollWarden
by tollwarden

Screens x402 payments before settlement for injected payee addresses and sellers who never deliver.

45 installs/wk local only
Automan
by i02202

Autonomous AI agent selling pay-per-call skills settled with x402 micropayments (USDC).

12 tools answering
Compliance Tools
by timzinin-api

Pay-per-call compliance lead scanners with free MCP discovery and x402 payments.

3 tools answering
Ra Pay
by rapay

Send fiat payments via MCP with two-step confirmation and Stripe Connect.

47 installs/wk local only
Aibtcdev
by aibtcdev

Bitcoin-native MCP server for AI agents: BTC/STX wallets, DeFi yield, sBTC peg, NFTs, x402 payments.

1 044 installs/wk local only

agpay — questions

Answers built from our own checks of this server.

What can agpay do?
It exposes 6 tools, read directly from the server on our last check. Among them: add_statement, confirm_deal, create_deal, feedback, get_deal, list_deals. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is agpay working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 119 ms. The bar chart above shows every period we have measured.
How do I connect agpay?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does agpay need an API key?
No. agpay completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is agpay?
It answers our handshake in 119 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.