Paybond MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 390 installs a week from pypi. Last commit 21 Sep 2026.
Default trust layer for agentic payments: authorize agent spend, evidence, receipts, settlement.
What the code does
We read the source, 4 d 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.
этот файл ставится пользователю, но в репозитории его нет
const child = spawn(command, args, { stdio: "ignore", detached: true });
result = subprocess.run(
document.getElementById("banner-root").innerHTML = renderBanner(hasCredentials, events.length > 0);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
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.
Connect this server
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 paybond -e 'PAYBOND_API_KEY=<PAYBOND_API_KEY>' -- npx -y @paybond/kit{
"mcpServers": {
"paybond": {
"command": "npx",
"args": [
"-y",
"@paybond/kit"
],
"env": {
"PAYBOND_API_KEY": "<PAYBOND_API_KEY>"
}
}
}
}[mcp_servers.paybond]
command = "npx"
args = ["-y", "@paybond/kit"]
env = { PAYBOND_API_KEY = "<PAYBOND_API_KEY>" }{
"mcpServers": {
"paybond": {
"command": "npx",
"args": [
"-y",
"@paybond/kit"
],
"env": {
"PAYBOND_API_KEY": "<PAYBOND_API_KEY>"
}
}
}
}{
"servers": {
"paybond": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@paybond/kit"
],
"env": {
"PAYBOND_API_KEY": "<PAYBOND_API_KEY>"
}
}
}
}Put your own value in place of
<PAYBOND_API_KEY> (Paybond service-account API key for the tenant-bound MCP session).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
PAYBOND_GATEWAY_URL (Optional Paybond gateway base URL. Defaults to the hosted Paybond API), PAYBOND_ENV_FILE (Optional local env file path used to load PAYBOND_API_KEY when the host does not set it directly).
Alternatives to Paybond MCP Server
same job, measured the same wayTrust scores and on-chain payment receipts for x402 services.
x402 payment wrapper for AI Agents and MCP Servers. USDC settlements on Base L2.
Trust layer for AI agents: identity, guard, redact, escrow, and x402 payments.
MCP server for YooKassa payment API — payments, refunds, receipts (54-FZ). 10 tools. First MCP for
Trust OS for AI agents: governed memory, payments, reputation, approvals, and audit evidence.
Marketplace and payment rail for AI agents: list, buy and settle with signed receipts.
Authorize and prove autonomous x402/AP2 agent payments with cryptographic receipts.
Read-only Site Rep handoff: agent brief, pending work, first-customer receipt with payment evidence.
Paybond MCP Server — questions
Answers built from our own checks of this server.