# Beggar Bot (mcpb · beggar-bot-mcp-0.1.0.mcpb)

x402 utilities on Base: USDC payment verification, risk scores, signed receipts ($0.01 USDC/call).

- Trust score: 42/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `beggar-bot-mcp-0.1.0.mcpb`: 42/100 (this document), [markdown](https://verifymcp.io/servers/beggar-bot-x402-beggar-bot-mcp/beggar-bot-mcp.md), [page](https://verifymcp.io/servers/beggar-bot-x402-beggar-bot-mcp/beggar-bot-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/beggar-bot-x402/beggar-bot-mcp/releases/download/v0.1.0/beggar-bot-mcp-0.1.0.mcpb`
- Transport: `stdio`
- SHA-256: `d3b8d23afc8fe3e743ec86d3d49e84d60213df531084bd7cbe0ad44d54d9d536`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 23/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 346 tokens (~86/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Beggar Bot MCP server?

Beggar Bot ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, d3b8d23afc8fe3e743ec86d3d49e84d60213df531084bd7cbe0ad44d54d9d536; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/beggar-bot-x402/beggar-bot-mcp/releases/download/v0.1.0/beggar-bot-mcp-0.1.0.mcpb`
- SHA-256: `d3b8d23afc8fe3e743ec86d3d49e84d60213df531084bd7cbe0ad44d54d9d536`

### Verify on macOS / Linux

```bash
echo "d3b8d23afc8fe3e743ec86d3d49e84d60213df531084bd7cbe0ad44d54d9d536  beggar-bot-mcp-0.1.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\beggar-bot-mcp-0.1.0.mcpb).Hash -eq "d3b8d23afc8fe3e743ec86d3d49e84d60213df531084bd7cbe0ad44d54d9d536"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 42)

First indexed and scored.

## MCP tools (4)

### `verify_payment` (~117 tokens)

Check that a USDC payment payer->payee for an exact amount landed on Base (paid: $0.01 via x402).

Input parameters:

- `amount` (string, required): USDC decimal, e.g. 0.01
- `invoice` (string, required)
- `lookback_blocks` (integer)
- `network` (string): default base
- `payee` (string, required)
- `payer` (string, required)
- `x_payment` (string): optional base64 X-PAYMENT header from your own x402 wallet client

### `risk_score` (~82 tokens)

Risk score for a Base address or an x402 endpoint manifest (paid: $0.01 via x402). Give address or endpoint.

Input parameters:

- `address` (string)
- `endpoint` (string)
- `network` (string): default base
- `x_payment` (string): optional base64 X-PAYMENT header from your own x402 wallet client

### `signed_receipt` (~114 tokens)

Ed25519-signed, hash-chained receipt for a verified Base USDC payment tx (paid: $0.01 via x402).

Input parameters:

- `amount` (string, required)
- `invoice` (string)
- `network` (string): default base
- `payee` (string, required)
- `payer` (string, required)
- `resource` (string)
- `tx_hash` (string, required)
- `x_payment` (string): optional base64 X-PAYMENT header from your own x402 wallet client

### `verify_receipt` (~33 tokens)

Verify a Beggar Bot receipt signature (free).

Input parameters:

- `receipt` (object, required)
- `signature` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/beggar-bot-x402-beggar-bot-mcp/beggar-bot-mcp#diagnostics

## Score history

- 2026-11-05: 42
- 2026-11-04: 42
- 2026-11-03: 42
- 2026-11-02: 42
- 2026-11-01: 42
- 2026-10-31: 42
- 2026-10-30: 42
- 2026-10-29: 42
- 2026-10-28: 42
- 2026-10-27: 42
- 2026-10-26: 42
- 2026-10-25: 42
- 2026-10-24: 42

## Common questions

### What is the Beggar Bot MCP server?

Beggar Bot is an MCP server listed in the public MCP registry as io.github.beggar-bot-x402/beggar-bot-mcp. x402 utilities on Base: USDC payment verification, risk scores, signed receipts ($0.01 USDC/call). This page covers its MCPB bundle (https://github.com/beggar-bot-x402/beggar-bot-mcp/releases/download/v0.1.0/beggar-bot-mcp-0.1.0.mcpb).

### Is the Beggar Bot MCP server safe to use?

Beggar Bot scores 42 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Beggar Bot MCP server expose?

Beggar Bot exposes 4 tools: verify_payment, risk_score, signed_receipt, verify_receipt. Their descriptions and schemas cost roughly 346 tokens of context every time the server is loaded.

### What licence is the Beggar Bot MCP server under?

Beggar Bot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/beggar-bot-x402/beggar-bot-mcp
- Website: https://beggar-bot-demand.beggarbot.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/beggar-bot-x402-beggar-bot-mcp/beggar-bot-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/beggar-bot-x402-beggar-bot-mcp/beggar-bot-mcp.json
- HTML version of this page: https://verifymcp.io/servers/beggar-bot-x402-beggar-bot-mcp/beggar-bot-mcp