MCP.Market

BitBooth Seller Routes MCP server

by Drock91·io.github.Drock91/bitbooth-routes·v1.1.1

Create private x402 seller routes, set prices, and route payouts directly to your wallets.

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

0 stars24 downloads/wk

Reviews

Write one

Nobody has reviewed BitBooth Seller Routes yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

BitBooth Seller Routes tools (5, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • create_routewrite action

    Register a new x402-paywalled endpoint. Returns the saved route.

  • delete_routewrite action

    Permanently remove a route. Agents that try to call this path afterwards will get a 404.

  • list_routes

    List every paid route registered under the authenticated tenant.

  • preview_route

    Returns the exact PaymentChallenge an agent would see when calling this saved

  • update_routewrite action

    Idempotent upsert keyed by path. Use this for both initial creation and

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • Code scan8 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 29 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How BitBooth Seller Routes compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
60%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
24
more than 10% of 12,191 servers with a package

What its tools let an agent do: 2 read · 1 create · 1 change · 1 delete

Install BitBooth Seller Routes in Claude Code, Cursor or VS Code

Runs npx -y @bitbooth/mcp-routes on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add bitbooth-routes -- npx -y @bitbooth/mcp-routes
Add to Cursor

What the publisher says

From the BitBooth Seller Routes repository's README, as published. We do not edit it. Read it on GitHub

BitBooth

BitBooth's featured product is PageDelta, a paid page observation API for agents.

POST https://app.heinrichstech.com/v1/cdp/render-pro
$0.01 per observation

A buyer does not need a BitBooth account or subscription. Send a page URL, inspect the x402 challenge, pay with a supported stablecoin rail, and receive rendered Markdown plus bounded change evidence.

Live links: PageDelta browser demo | featured catalog | API docs | MCP package

What PageDelta does

The first paid observation saves a baseline scoped to the payer, canonical URL, and extraction mode. A later paid observation of the same scope compares the new result with that saved baseline.

Each successful response can include:

  • rendered, bounded Markdown
  • an exact, case-sensitive focus search result
  • a structured, bounded line diff
  • the prior baseline status and saved revision
  • a new opaque cursor for continuity checks
  • content and observation hashes
  • an optional bounded JPEG snapshot
  • settled payment metadata and a PAYMENT-RESPONSE receipt

The cursor is not an access token, and returned web content is untrusted input. Agents should still apply their own prompt-injection and data-handling policy.

Inspect the live challenge

This request does not pay. It returns HTTP 402 with the current payment requirements in the PAYMENT-REQUIRED header.

curl -i -X POST https://app.heinrichstech.com/v1/cdp/render-pro \
  -H 'content-type: application/json' \
  -d '{"url":"https://example.com","extract":"article","focus":"Example Domain"}'

For production PageDelta, the advertised rails are:

The fresh 402 challenge is authoritative for the exact network identifier, asset or issuer, amount, recipient, and timeout. PageDelta does not advertise a Solana rail.

Try the complete flow without real money

Open the PageDelta browser demo. It runs an isolated XRPL Testnet exercise:

  1. The tab creates a temporary wallet in browser memory.
  2. The official faucet funds it with valueless test XRP.
  3. The first observation pays 1,000 test drops and saves a payer-scoped baseline.
  4. The demo changes its isolated page from revision 1 to revision 2.
  5. The second observation pays another 1,000 test drops and returns the change.
  6. The run ends with two XRPL Testnet receipts.

Confirmation retries reuse the same signed proof. They do not create additional payments. This demo proves the test flow only. It is not a production payment and does not represent revenue.

Use the MCP buyer

The current buyer is @bitbooth/mcp-fetch@2.3.1. Its official MCP registry name is io.github.Drock91/bitbooth-fetch.

For free catalog discovery, no wallet credential is required:

{
  "mcpServers": {
    "bitbooth": {
      "command": "npx",
      "args": ["-y", "@bitbooth/mcp-fetch@2.3.1"]
    }
  }
}

The packaged PageDelta buyer currently automates the XRPL mainnet RLUSD path. Enabling it requires an explicit xrpl-rlusd rail, a dedicated low-balance XRPL wallet, and a per-call limit of at least 0.010000. See the integration guide before adding a seed.

Discovery scope

https://app.heinrichstech.com/bazaar.json currently features exactly one resource: PageDelta at /v1/cdp/render-pro.

That featured catalog is a deliberate release surface. It is not a count of everything implemented inside BitBooth. Internal and reference routes may exist outside it, and private seller routes are not automatically published there.

XRPL ecosystem status

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

BitBooth Seller Routes: common questions

Is BitBooth Seller Routes MCP server safe?
Mostly: it is graded B (83/100). Read the BitBooth Seller Routes safety report
How do I install BitBooth Seller Routes?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does BitBooth Seller Routes need an API key?
Yes. The registry entry asks for BITBOOTH_API_KEY.
Is BitBooth Seller Routes maintained?
The last commit was 49 days ago (2026-09-16). The latest release is v1.1.1.
How does BitBooth Seller Routes compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 60% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.