Beggar Bot
LocalAbout Beggar Bot
Beggar Bot is an MCP server for x402 utilities on Base, aimed at clients that need to verify USDC payments, obtain risk scores, or issue signed receipts. Three operations cost $0.01 USDC per call; receipt verification is free, and the server does not hold keys or make payments.
Key features
- 01USDC payment verification
- 02Risk scoring
- 03Signed receipt creation
- 04Free receipt verification
- 05x402 payments on Base
Use cases
- 01Checking a USDC payment on Base
- 02Assessing transaction risk
- 03Issuing a signed receipt
- 04Validating an existing receipt
MCP support
The MCP server exposes payment verification, risk scoring, receipt creation, and receipt verification tools. Paid calls require clients to provide an x402 payment in the `x_payment` argument; the server does not pay on their behalf.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEbeggar-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
| Tool | Route | Price |
|---|---|---|
verify_payment | GET /v1/verify | $0.01 USDC (Base, x402) |
risk_score | GET /v1/risk | $0.01 USDC (Base, x402) |
signed_receipt | POST /v1/receipt | $0.01 USDC (Base, x402) |
verify_receipt | POST /v1/receipt/verify | free |
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)
{
"mcpServers": {
"beggar-bot": {
"command": "npx",
"args": ["-y", "github:beggar-bot-x402/beggar-bot-mcp"]
}
}
}
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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.