
Bitbooth Fetch MCP
- Updated May 13, 2026
- Drock91/bitbooth-docs
bitbooth-fetch is a MCP server that fetches any URL as clean markdown for 0.005 USDC per request via x402 without API keys.
About
bitbooth-fetch is a Model Context Protocol server that lets coding agents retrieve web pages as clean markdown by paying 0.005 USDC per fetch through the x402 protocol, using an agent-controlled wallet instead of vendor API keys. developers in the Idea phase use it for competitor teardowns, pricing page captures, and documentation snapshots when spinning up research threads in Claude Code or Cursor—you avoid maintaining headless browser infrastructure for every ad-hoc URL. Setup requires a hex-encoded BITBOOTH_AGENT_KEY for the paying wallet; defaults target Base Sepolia testnet so you can experiment without mainnet USDC, with BITBOOTH_CHAIN_ID=8453 documented for real spends on Base. Intermediate complexity: you must be comfortable with crypto env vars and per-fetch costs. It complements manual browsing skills; it is not a full compliance web crawler or authenticated session scraper for logged-in SaaS dashboards.
- x402 micropayment: 0.005 USDC per fetch through BitBooth gateway
- Returns clean markdown for any URL—no traditional scrape API keys
- Agent wallet via BITBOOTH_AGENT_KEY; default Base Sepolia testnet, mainnet chain ID 8453 optional
- npm package @bitbooth/mcp-fetch with stdio MCP transport
- Configurable BITBOOTH_API_URL and BITBOOTH_CHAIN_ID for staging vs Base mainnet
Bitbooth Fetch MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add --env BITBOOTH_AGENT_KEY=YOUR_BITBOOTH_AGENT_KEY --env BITBOOTH_API_URL=YOUR_BITBOOTH_API_URL --env BITBOOTH_CHAIN_ID=YOUR_BITBOOTH_CHAIN_ID bitbooth-fetch -- npx -y @bitbooth/mcp-fetchAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | @bitbooth/mcp-fetch |
|---|---|
| Transport | STDIO |
| Auth | Required |
| Last updated | May 13, 2026 |
| Repository | Drock91/bitbooth-docs ↗ |
What it does
Pay per URL fetch in USDC via x402 so your agent gets clean markdown for competitor pages and docs without managing scrape API keys.
Who is it for?
Crypto-comfortable developers who want metered, agent-driven web reads during market and competitor research.
Skip if: Skip if you cannot use wallet keys, need guaranteed zero-cost fetching, or require authenticated behind-login scraping.
What you get
Your agent fetches URLs as markdown with per-request USDC payment and no separate scrape vendor API key.
- Clean markdown representation of a fetched public URL
- Per-fetch x402 payment flow without separate scrape API credentials
- Agent-ready web reads for research prompts and competitive notes
By the numbers
- 0.005 USDC per fetch
- Default chain ID 84532 (Base Sepolia); 8453 for Base mainnet
- MCP package version 1.0.3 (@bitbooth/mcp-fetch)
README.md
BitBooth
The multi-chain x402 payment gateway for AI agents. 18 paid HTTP endpoints, 5 mainnet chains, real on-chain settlement, ~$2/month to run on AWS Lambda.
Live: app.heinrichstech.com Playground: app.heinrichstech.com/demo API reference: app.heinrichstech.com/docs Bazaar manifest: app.heinrichstech.com/bazaar.json A2A agent card: app.heinrichstech.com/.well-known/agent.json
What is this?
BitBooth implements the x402 protocol — Coinbase's spec for "HTTP 402 Payment Required + on-chain settlement." Drop a paywall in front of any HTTP endpoint, and AI agents pay per call from their own wallet. No accounts, no API keys, no signups. Non-custodial — the agent pays your wallet directly, BitBooth never touches the funds.
1. Agent calls a paywalled endpoint with no payment
2. Server returns HTTP 402 with a multi-chain `accepts[]` array
3. Agent picks one entry (whatever chain it holds liquidity on) and signs
4. Agent retries the request with X-PAYMENT header
5. Server verifies + settles + unlocks the response
The whole loop is ~3 seconds on Base mainnet.
Why multi-chain?
Every BitBooth endpoint advertises up to 9 (network, asset) tuples in every 402 challenge:
| Network | Asset | Facilitator |
|---|---|---|
| Base mainnet (eip155:8453) | USDC | Coinbase CDP |
| Base mainnet | Chainlink LINK | Self-hosted onchain verifier |
| Solana mainnet | USDC SPL | Coinbase CDP |
| XRPL native (xrpl:0) | XRP | T54 XRPL Facilitator |
| XRPL native | RLUSD (Ripple issuer) | T54 |
| XRPL native | USDC IOU (Bitstamp issuer) | T54 |
| Stellar pubnet | XLM | Self-hosted Horizon |
| Stellar pubnet | USDC (Circle issuer) | Self-hosted Horizon |
| XRPL EVM Sidechain (eip155:1440000) | Native XRP | Self-hosted onchain verifier |
Agents pick the chain they already hold. No bridging, no swaps, no friction.
Quick start
Pay one endpoint with curl (no payment yet — see the 402 challenge)
curl -s -X POST https://app.heinrichstech.com/v1/cdp/echo \
-H 'content-type: application/json' \
-d '{"message":"hello from agent"}'
You'll get back a 402 response body containing resource, accepts[], and an extensions.bazaar block.
Install the MCP server for any Claude / Cursor / Continue agent
npm install -g @bitbooth/mcp-fetch
Or in your MCP client config (Claude Desktop, Cursor, etc.):
{
"mcpServers": {
"bitbooth": {
"command": "npx",
"args": ["-y", "@bitbooth/mcp-fetch"],
"env": {
"BITBOOTH_AGENT_KEY": "0x<your-testnet-wallet-private-key>"
}
}
}
}
Testnet by default (Base Sepolia). Opt into mainnet explicitly with BITBOOTH_CHAIN_ID=8453.
Or build your own buyer
See examples/ for runnable demos:
01-curl-fetch.sh— pure shell, sees the 402 challenge02-node-evm-pay.mjs— Node + ethers, signs EIP-3009 transferWithAuthorization on Base03-node-xrpl-pay.mjs— Node + xrpl.js, signs an XRPL Payment tx through the T54 facilitator04-mcp-config.json— drop-in MCP client config05-langchain-agent.py— LangChain agent that fetches paid URLs
The endpoint catalog
| Endpoint | Price | Category |
|---|---|---|
/v1/cdp/echo |
$0.001 | utility |
/v1/cdp/json-repair |
$0.001 | utility |
/v1/cdp/faker |
$0.001 | utility |
/v1/cdp/jwt-verify |
$0.001 | utility |
/v1/cdp/webhook-sig-verify |
$0.001 | utility |
/v1/cdp/llm-tool-validate |
$0.002 | utility |
/v1/cdp/pii-redact |
$0.002 | utility |
/v1/cdp/rss |
$0.002 | data |
/v1/cdp/dns |
$0.002 | utility |
/v1/cdp/ssl-info |
$0.002 | security |
/v1/cdp/x402-discover |
$0.005 | security |
/v1/cdp/agent-credit-score |
$0.005 | security |
/v1/cdp/wallet-doctor |
$0.005 | security |
/v1/cdp/prompt-injection-scan |
$0.005 | security |
/v1/cdp/contract-honeypot-check |
$0.005 | security |
/v1/cdp/approval-safety |
$0.05 | security |
/v1/cdp/render-pro |
$0.05 | data |
/v1/cdp/web-diff |
$0.08 | data |
Full schemas in openapi.yaml. Live manifest at /bazaar.json.
Documentation
docs/INTEGRATION.md— integration guide (buyer + seller patterns)docs/ENDPOINTS.md— full endpoint catalog with examplesdocs/XRPL.md— XRPL native + XRPL EVM Sidechain integration notesopenapi.yaml— full OpenAPI spec for every paid endpointexamples/— runnable demos
About
BitBooth is built and operated by Heinrichs Software Solutions Company — a veteran-owned business based in Tallahassee, Florida. SDVOSB-pending, CAGE-registered, SAM.gov-registered. Solo-built. Production-grade testing (~2,400+ Vitest tests, 92% coverage on core payment + middleware paths). Approved under Anthropic's Cyber Verification Program for dual-use cybersecurity work.
License
MIT — see LICENSE.
This repository contains the public documentation, OpenAPI spec, and runnable examples for BitBooth. The gateway source code is operated privately during a federal-procurement-posture scrub; for technical-interview-grade source access, contact derek@heinrichstech.com.
Recommended MCP Servers
How it compares
x402 pay-per-fetch MCP, not a self-hosted Playwright skill or unlimited flat-rate scrape API.
FAQ
Who is bitbooth-fetch for?
Agent users doing Idea-phase research who accept USDC micropayments per page and want markdown output without API key signup.
When should I use bitbooth-fetch?
Use it when your agent must read public competitor sites, docs, or articles during validation and you prefer 0.005 USDC per fetch over maintaining scrape infrastructure.
How do I add bitbooth-fetch to my agent?
Install @bitbooth/mcp-fetch, set BITBOOTH_AGENT_KEY to your agent wallet private key, optionally set BITBOOTH_CHAIN_ID and BITBOOTH_API_URL, then register the package as a stdio MCP server.