bitcoin-mcp
bitcoin-mcp is an MCP (Model Context Protocol) server that lets AI agents interact with the Bitcoin and Lightning Network ecosystems—e.g., generating keys, validating addresses, decoding raw Bitcoin transactions, querying blockchain data, decoding BOLT11 invoices, and paying Lightning invoices via LNBits.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Based on the provided README/manifest, there is no documented authentication/authorization for the MCP server, and no explicit guidance on preventing private key/WIF leakage. TLS enforcement and rate limits are not described. Dependencies include common Node packages (e.g., express, cors, pino), but the provided content does not show vulnerability management (lockfile/CVE scan) or security configuration details.
⚡ Reliability
Best When
You want an agent to call well-defined MCP tools for Bitcoin/Lightning inspection and (optionally) Lightning invoice payment in a local/controlled environment (Claude Desktop/Goose).
Avoid When
You need strong, documented authentication/authorization boundaries, audited security around key material, or guaranteed operational reliability/SLA for production workloads.
Use Cases
- • Letting an AI assistant query Bitcoin blockchain data (latest block, transaction details)
- • Assisting with Bitcoin key/address generation and address validation workflows
- • Enabling AI-assisted decoding/explanation of raw Bitcoin transactions
- • Parsing/understanding BOLT11 Lightning invoices via MCP tools
- • Automating Lightning payments from an agent through an LNBits-connected workflow
Not For
- • Custodial wallet operations or production-grade key management without additional security controls
- • Handling untrusted, sensitive secrets (private keys) without secure storage and strict redaction
- • Transaction creation/broadcast workflows if this server’s toolset is intended to be read-only/decoding-focused (based on README it’s more query/decode than full node-backed broadcasting)
Interface
Authentication
No authentication/authorization mechanism is described in the provided README content for the MCP server itself. Lightning payment mentions LNBits but does not describe auth handling in detail.
Pricing
Open-source npm package; any costs depend on external dependencies such as network providers, LNBits, or infrastructure you run.
Agent Metadata
Known Gotchas
- ⚠ Lightning payment via LNBits may require careful handling of secrets and could be non-idempotent
- ⚠ If using SSE mode, connectivity and correct endpoint/URL shape are easy failure points (README gives conventions but not concrete server routes)
- ⚠ Key generation tools could lead agents to expose sensitive private key material unless tool outputs are constrained/redacted
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for bitcoin-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.