
Beggar Bot
io.github.beggar-bot-x402Published by GitHub account beggar-bot-x402v0.1.0Updated Oct 24, 2026
x402 utilities on Base: USDC payment verification, risk scores, signed receipts ($0.01 USDC/call).
Overview
A local MCP server exposing Beggar Bot's pay-per-call x402 utilities on Base: USDC payment verification, risk scores and signed receipts.
- What you can do
- Verify USDC payments through the verify_payment tool, which checks a payment against the service's verification route for a fee per call. Retrieve risk scores for an address or payment via risk_score. Create signed receipts with signed_receipt and check them for free with verify_receipt. When a paid tool is called without payment proof, the server returns the x402 payment requirements instead of a result.
- When to use it
- Useful when an assistant needs to check USDC payments on Base, obtain a risk score, or issue and verify signed receipts, and the user is willing to pay a small per-call fee in USDC through x402.
- Requirements
- Runs locally over stdio; the README lists Node.js 18 or later and an npx or local checkout launch. Network access to the Beggar Bot service is needed, and BEGGAR_BOT_URL can point at a different deployment. Paid calls need an X-PAYMENT header built with the user's own x402 client and passed as x_payment.
Installation
In SourceWeft
- Open Beggar Bot 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
beggar-bot-mcp
MCP server for Beggar Bot, a set of pay-per-call x402 utilities on Base: USDC payment verification, risk scores, and signed receipts. Each paid call costs $0.01 USDC on Base through the x402 protocol.
The server holds no keys and never pays anything itself. If you call a paid tool without x_payment, it returns the HTTP 402 x402 payment requirements. To pay, build an X-PAYMENT header with your own x402 client (for example x402-fetch) and pass it as x_payment.
Tools
Live service: https://beggar-bot-demand.beggarbot.workers.dev
- https://beggar-bot-demand.beggarbot.workers.dev/v1/verify
- https://beggar-bot-demand.beggarbot.workers.dev/v1/risk
- https://beggar-bot-demand.beggarbot.workers.dev/v1/receipt
- https://beggar-bot-demand.beggarbot.workers.dev/v1/receipt/verify (free)
MCP client config (Claude Desktop, Cursor, or any stdio MCP client)
Requires Node.js 18 or later. Set BEGGAR_BOT_URL to point at a different deployment.
From a local checkout: npm install, then "command": "node", "args": ["/path/to/beggar-bot-mcp/index.js"].
Discovery
- x402scan: https://www.x402scan.com/server/161aa10d-fa13-46d1-80aa-e2d1c32be6dd
- x402 manifest: https://beggar-bot-demand.beggarbot.workers.dev/.well-known/x402
- OpenAPI: https://beggar-bot-demand.beggarbot.workers.dev/openapi.json
- llms.txt: https://beggar-bot-demand.beggarbot.workers.dev/llms.txt
- Agent card: https://beggar-bot-demand.beggarbot.workers.dev/.well-known/agent.json
- Contact: [email protected]
License
MIT
Source: README.md at commit 7bf7fff
Tools
0Version history
1- v0.1.0LatestOct 24, 2026
Score
50% 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
- License10 pts