Burnbound runs on your own machine — the client starts it, so there is no endpoint to ping. 374 installs a week from npm.
Let your AI agent pay x402 APIs within daily caps, allowed hosts and human approval.
Today is the operative word: we check Burnbound every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
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 mcp -e 'BURNBOUND_KEY=<BURNBOUND_KEY>' -- npx -y @burnbound/mcp
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@burnbound/mcp"
],
"env": {
"BURNBOUND_KEY": "<BURNBOUND_KEY>"
}
}
}
}
[mcp_servers.mcp]
command = "npx"
args = ["-y", "@burnbound/mcp"]
env = { BURNBOUND_KEY = "<BURNBOUND_KEY>" }
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@burnbound/mcp"
],
"env": {
"BURNBOUND_KEY": "<BURNBOUND_KEY>"
}
}
}
}
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@burnbound/mcp"
],
"env": {
"BURNBOUND_KEY": "<BURNBOUND_KEY>"
}
}
}
}
Put your own value in place of
<BURNBOUND_KEY> (Agent key (bb_agent_…) created in the Burnbound dashboard. Sent only to the Burnbound API).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
BURNBOUND_API (Burnbound API base URL. https:// only (http:// only for loopback). Set it for a self-hosted or local API), BURNBOUND_AGENT_ID (Only with an org key instead of an agent key: the agent the tools act for. Ignored with an agent key), BURNBOUND_WALLET_PROFILE (Local wallet profile for client-side signing (created with `npx -y @burnbound/mcp wallet init`). 1–32 of a-z, 0-9, _ and -), BURNBOUND_HOME (Directory for the local wallet file when the OS keychain is not used), BURNBOUND_MAX_RESPONSE_BYTES (fetch_paid response body cap in bytes (maximum 10485760). Longer bodies are truncated), BURNBOUND_FETCH_TIMEOUT_MS (fetch_paid deadline for the whole exchange with the URL, between 1000 and 120000 ms), BURNBOUND_APP_URL (Origin of the Burnbound panel, for the approval link a held payment returns (and opens in clients with URL-mode elicitation). Default: the API origin when it is https. https:// only), BURNBOUND_APPROVAL_WAIT_MS (How long fetch_paid waits for the human's decision once the approval page is opened from the chat, between 0 and 50000 ms. 0 returns pending_approval at once), BURNBOUND_BASE_RPC_URL (diagnose_payment: Base RPC used to read the paying wallet's USDC balance. https:// only. Only the wallet address is sent to it), BURNBOUND_BASE_SEPOLIA_RPC_URL (diagnose_payment: Base Sepolia RPC used to read the paying wallet's USDC balance. https:// only).
Set up human approval for your AI agents' tool calls.
Your agent posts, schedules, queues and threads posts on X, with a human approval queue.
Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.
Pink Agentic AI Payments: AI agents pay within spending rules (budgets, caps, approval). Sandbox.
Budgets, payee allowlists, price-spike checks and human approval for agents paying x402 paywalls
AI agent payments with human approval. Local-first, encrypted credentials, budget controls.
Let your AI assistant pay for web content in USDC (x402) within a budget you set.
Troubleshoot enrolled client PCs from your AI client, with human approval and an audit trail.
Answers built from our own checks of this server.