Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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).

0 this week 42 Trust /100

Last scanned (9 hours ago)

Scores higher than 73% of MCPB servers

Category Crypto and Web3

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security23
  • 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.Unverified
  • Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 346 tokens (~86/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Oct 26 42

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed mcpb/https://github.com/beggar-bot-x402/beggar-bot-mcp/releases/download/v0.1.0/beggar-bot-mcp-0.1.0.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~346 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
risk_score ~82

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

NameTypeReqDescription
addressstring––
endpointstring––
networkstring–default base
x_paymentstring–optional base64 X-PAYMENT header from your own x402 wallet client

No output schema declared.

No examples provided.

signed_receipt ~114

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

NameTypeReqDescription
amountstringyes–
invoicestring––
networkstring–default base
payeestringyes–
payerstringyes–
resourcestring––
tx_hashstringyes–
x_paymentstring–optional base64 X-PAYMENT header from your own x402 wallet client

No output schema declared.

No examples provided.

verify_payment ~117

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

NameTypeReqDescription
amountstringyesUSDC decimal, e.g. 0.01
invoicestringyes–
lookback_blocksinteger––
networkstring–default base
payeestringyes–
payerstringyes–
x_paymentstring–optional base64 X-PAYMENT header from your own x402 wallet client

No output schema declared.

No examples provided.

verify_receipt ~33

Verify a Beggar Bot receipt signature (free).

NameTypeReqDescription
receiptobjectyes–
signaturestringyes–

No output schema declared.

No examples provided.

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.

mcpb · beggar-bot-mcp-0.1.0.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

d3b8d23afc8fe3e743ec86d3d49e84d60213df531084bd7cbe0ad44d54d9d536

macOS / Linux

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

Windows (PowerShell)

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

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

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.