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.

BitBooth Agent Tools

NPM · @BITBOOTH/MCP-FETCH · SCANNED SEP 24

Discover BitBooth APIs for free, then buy capped x402 fetch, PageDelta, and wallet checks.

Available components

npm · @bitbooth/mcp-fetch 77
+3 this week 77 Trust /100
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 Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 33 of 124 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 331 tokens (~165/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
Install

How do I install the BitBooth Agent Tools MCP server?

BitBooth Agent Tools runs locally as an npm package, launched with npx -y @bitbooth/mcp-fetch. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @bitbooth/mcp-fetch

# add to Claude Code
claude mcp add drock91-bitbooth-fetch -- npx -y @bitbooth/mcp-fetch
// .cursor/mcp.json
{
  "mcpServers": {
    "drock91-bitbooth-fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@bitbooth/mcp-fetch"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "drock91-bitbooth-fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@bitbooth/mcp-fetch"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add drock91-bitbooth-fetch -- npx -y @bitbooth/mcp-fetch
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "drock91-bitbooth-fetch": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@bitbooth/mcp-fetch"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add drock91-bitbooth-fetch --command npx --arg -y --arg @bitbooth/mcp-fetch
# ~/.hermes/config.yaml
mcp_servers:
  drock91-bitbooth-fetch:
    command: "npx"
    args: ["-y", "@bitbooth/mcp-fetch"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "drock91-bitbooth-fetch": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@bitbooth/mcp-fetch"
      ]
    }
  }
}
# add to Vellum
assistant mcp add drock91-bitbooth-fetch -t stdio -c npx -a -y @bitbooth/mcp-fetch
// mcp.json
{
  "mcpServers": {
    "drock91-bitbooth-fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@bitbooth/mcp-fetch"
      ]
    }
  }
}
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.

  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Supply Chain Security rose 1.

  • 13 Sept 26 +16
    • Malware scan: unverified → pass ▲ security
  • 12 Sept 26 0
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 2.3.0 → 2.3.1 functional
  • 11 Sept 26 +18
    • Malware scan: pass → unverified ▼ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 1.0.3 → 2.3.0 functional
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 24 Sept 2026 · Analysed npm/@bitbooth/mcp-fetch@2.3.1

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 124 packages
Packages resolved 124
Stale 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~297 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
discover_bitbooth ~171

Search the live BitBooth x402 catalog by capability, category, price, network, or asset. This is a read-only discovery call: it never signs or submits a payment.

NameTypeReqDescription
assetstring–Only return routes advertising this exact asset identifier
categorystring–Exact catalog category, such as utility or data
configuredOnlyboolean–Filter to the MCP server configured payment network and asset
limitinteger–Maximum number of matching resources to return
maxPriceUsdnumber–Only return routes at or below this stablecoin-denominated USD price
networkstring–Only return routes advertising this CAIP-2 network
querystring–Text to match against route names, paths, summaries, networks, and assets

No output schema declared.

No examples provided.

preflight_bitbooth ~126

Select a catalog payment requirement for a route under a hard price ceiling. Uses the configured payment rail; explicit network or asset filters narrow that rail but do not reconfigure it. Never signs or pays.

NameTypeReqDescription
assetstring–Explicit asset identifier; must also match the configured buyer rail
maxPriceUsdnumberyesHard maximum stablecoin-denominated USD price for this call
networkstring–Explicit CAIP-2 network; must also match the configured buyer rail
routestringyesExact catalog route name, path, or URL

No output schema declared.

No examples provided.

Common questions

What is the BitBooth Agent Tools MCP server?

BitBooth Agent Tools is an MCP server listed in the public MCP registry as io.github.Drock91/bitbooth-fetch. Discover BitBooth APIs for free, then buy capped x402 fetch, PageDelta, and wallet checks. This page covers its npm package (@bitbooth/mcp-fetch).

Is the BitBooth Agent Tools MCP server safe to use?

BitBooth Agent Tools scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. 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 BitBooth Agent Tools MCP server expose?

BitBooth Agent Tools exposes 2 tools: discover_bitbooth, preflight_bitbooth. Their descriptions and schemas cost roughly 297 tokens of context every time the server is loaded.

Is the BitBooth Agent Tools MCP server still maintained?

BitBooth Agent Tools is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the BitBooth Agent Tools MCP server under?

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