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.

io.github.csacanam/comprabtc

NPM · COMPRABTC-MCP · SCANNED SEP 20

Non-custodial Bitcoin DCA for agent treasuries: approve USDT once, stack WBTC on Celo forever.

Available components

0 this week 82 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 Security98
  • 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
  • 31 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 38 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 490 tokens (~98/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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 io.github.csacanam/comprabtc MCP server?

io.github.csacanam/comprabtc runs locally as an npm package, launched with npx -y comprabtc-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · comprabtc-mcp

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

  • 20 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 19 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 18 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

  • 13 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 12 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 11 Sept 26 +1
    • Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/comprabtc-mcp@0.1.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 111 packages
Packages resolved 111
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~490 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
cancel_plan ~75

Stop the DCA plan immediately — signs cancelPlan() and, by default, also revokes the USDT allowance (approve 0) for a clean, double-locked exit. The WBTC already purchased stays in the wallet untouched.

NameTypeReqDescription
revoke_allowancebooleanAlso set the allowance to 0 (default true)

No output schema declared.

No examples provided.

create_plan ~210

Create (or OVERWRITE) the treasury's Bitcoin DCA plan — signs 2 on-chain transactions: approve(total budget) + createPlan. Get explicit operator/human approval on the exact numbers first. Non-custodial: funds stay in the wallet; the verified contract enforces amount and interval; purchased WBTC arrives at this same wallet; fees ($0.005 + 1%) come OUT of each installment. First purchase executes within ~1 minute. amount_per_run: $0.10-$50 USDT (pool-depth safety cap). interval_seconds >= 3600 (hourly). budget = amount × installments, must be <= USDT balance.

NameTypeReqDescription
amount_per_run_usdtnumberyesUSDT per purchase (e.g. 1)
interval_secondsintegeryesSeconds between purchases (3600=hourly, 86400=daily)
total_budget_usdtnumberyesTotal USDT to authorize (allowance cap = installments × amount)

No output schema declared.

No examples provided.

get_portfolio ~61

Bitcoin accumulated by a wallet's plan: execution history (each purchase with tx hash and sats), cost basis, live BTC price. Free, read-only, via the CompraBTC API.

NameTypeReqDescription
addressstringWallet (defaults to the configured treasury wallet)

No output schema declared.

No examples provided.

get_wallet_status ~76

Balances (USDT, CELO for gas, WBTC sats), remaining authorized budget (allowance) and the current DCA plan of a wallet. Free, read-only. ALWAYS call this before create_plan, renew_budget or cancel_plan.

NameTypeReqDescription
addressstringWallet to inspect (defaults to the configured treasury wallet)

No output schema declared.

No examples provided.

renew_budget ~68

Authorize a new total budget for the existing plan — signs one approve transaction. IMPORTANT: approve REPLACES the previous allowance (it does not add). Use when installments_left is low or purchases paused for exhausted budget.

NameTypeReqDescription
total_budget_usdtnumberyesNew total USDT to authorize

No output schema declared.

No examples provided.

Common questions

What is the io.github.csacanam/comprabtc MCP server?

io.github.csacanam/comprabtc is an MCP server listed in the public MCP registry as io.github.csacanam/comprabtc. Non-custodial Bitcoin DCA for agent treasuries: approve USDT once, stack WBTC on Celo forever. This page covers its npm package (comprabtc-mcp).

Is the io.github.csacanam/comprabtc MCP server safe to use?

io.github.csacanam/comprabtc scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 io.github.csacanam/comprabtc MCP server expose?

io.github.csacanam/comprabtc exposes 5 tools: get_wallet_status, get_portfolio, create_plan, renew_budget, cancel_plan. Their descriptions and schemas cost roughly 490 tokens of context every time the server is loaded.

Is the io.github.csacanam/comprabtc MCP server still maintained?

io.github.csacanam/comprabtc is still listed as active in the MCP registry. We last reached this channel on 20 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 io.github.csacanam/comprabtc MCP server under?

io.github.csacanam/comprabtc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.