Private payments for AI agents (MCP)
Give an AI agent a wallet that can pay without exposing its history: set up the Blackpool MCP server, choose which tools the agent may use, and keep its payments private on four chains.
Last updated November 6, 2026
Why an agent's wallet needs privacy
An agent that pays for things from a normal wallet publishes everything it does: which services it uses, who it pays, how much and how often. Anyone can follow that address, copy its strategy or see its balance. With Blackpool the agent keeps a private balance and pays any address from it, so its payments stop forming a public trail.
Set up the MCP server
The Blackpool CLI runs as a Model Context Protocol server. Add it to your agent app's MCP configuration:
{
"mcpServers": {
"blackpool": {
"command": "npx",
"args": ["-y", "@blackpool/cli@latest", "mcp"],
"env": {
"BLACKPOOL_KEY": "0x<agent-wallet-private-key>",
"BLACKPOOL_MCP_TOOLS": "balance,send,bridges"
}
}
}
}Use a separate wallet for the agent and fund it with the asset to shield plus a little gas for deposits. The server starts without a key, so the agent can read fees and routes before you fund anything.
What the agent can do
| Tool | What it does |
|---|---|
blackpool_balance | Private and public balances, per pool or on every chain |
blackpool_deposit | Shield funds from the agent wallet |
blackpool_send | Pay any address privately; the relayer pays gas |
blackpool_swap | Swap between the native coin and a stablecoin inside the pool |
blackpool_bridge | Move value privately to another chain, Solana included |
blackpool_bridges, blackpool_assets | Bridge history and available routes |
blackpool_recover | Sweep anything left on one-time burners back |
Every tool returns the same JSON as the CLI, with ok and a clear error when something is refused.
Keep the agent on a short leash
- Allow-list tools:
BLACKPOOL_MCP_TOOLS=balance,sendexposes only those two. - Read-only mode:
BLACKPOOL_MCP_READONLY=1lets the agent look but not move funds. - Limit the balance: the agent can only spend what the agent wallet holds.
- No blind retries: after a timeout the agent should check
blackpool_balanceorblackpool_bridgesbefore trying again. The full rules are in AGENTS.md.
Plan with the hosted server
A read-only server runs at https://mcp.blackpool.cash/mcp with no sign-in. It answers fees, minimums, bridge quotes, analytics and status, and serves the agent guide. It never receives keys, so agents can use it to plan and the local server to act.
Questions
Which agent apps does it work with?
Any app that supports the Model Context Protocol over stdio, which covers most desktop chat apps, coding assistants and agent frameworks. Apps that only support remote servers can use the hosted read-only endpoint for quotes, fees and status.
Does the wallet key leave the machine?
No. The local server runs on the same machine as the agent app, builds proofs there and only sends finished proofs to the relayer. The hosted endpoint never receives keys or signatures.
How do I stop the agent from spending too much?
Fund the agent wallet with only what it may spend, and expose only the tools it needs with BLACKPOOL_MCP_TOOLS, or use BLACKPOOL_MCP_READONLY=1 to allow reads only.
Where is the server listed?
In the official MCP Registry as cash.blackpool/blackpool and on Glama, where the server is built and tested from the open-source repository.
Next
Read the full agent guide, see the chains in private payments on every chain, or install the package from npm.