
Swarmpay
io.github.ginokinoPublished by GitHub account ginokinov0.4.4Updated Oct 24, 2026
Payment layer for AI agents. Send USDC, manage escrows on Base blockchain.
Overview
Swarmpay is a local MCP server that gives an AI assistant a payment layer for agents: sending USDC and managing escrows on the Base blockchain.
- What you can do
- Send USDC payments on the Base blockchain from an assistant-driven wallet flow. Create and manage escrows so funds are held until conditions are met. Create wallets through the Coinbase Developer Platform using the configured API credentials. Operate against either Base mainnet or Base Sepolia depending on the configured network. Collect fees to an admin wallet address when one is configured.
- When to use it
- Use it when an assistant needs to move USDC or hold funds in escrow between agents on Base, for example paying for agent services or settling conditional agreements. It is not a general wallet or trading tool.
- Requirements
- Runs as a local Python package (PyPI swarmpay) over stdio on a desktop machine. Needs Coinbase Developer Platform credentials in CDP_API_KEY_ID and CDP_API_KEY_SECRET, plus SWARMPAY_NETWORK set to base-mainnet or base-sepolia. SWARMPAY_ADMIN_WALLET is used for fee collection. Network access to Base and Coinbase services is required.
Installation
In SourceWeft
- Open Swarmpay in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.4.4LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.