mcp-name: io.satoshiapi/mcp
SatoshiAPI MCP Server ⚡
Model Context Protocol server for SatoshiAPI — Bitcoin intelligence via Lightning micropayments.
Pay-per-call Bitcoin data for AI agents: price, mempool fees, DCA signals, whale activity, market regime, risk score, and more. 10–200 sats per call via L402. No accounts, no API keys.
Hosted MCP Server (recommended)
Connect directly — no installation needed:
https://api.satoshiapi.io/mcp
Any MCP client (Claude, Cursor, etc.) can connect instantly. Payments are handled per-call via L402 Lightning.
Self-hosted (pip install)
pip install satoshiapi-mcp
Configure in Claude Desktop (~/.config/claude/claude_desktop_config.json):
{
"mcpServers": {
"satoshiapi": {
"command": "python3",
"args": ["-m", "satoshiapi_mcp"],
"env": {
"SATOSHIAPI_LND_REST": "https://your-lnd:8079",
"SATOSHIAPI_LND_MACAROON": "/path/to/invoice.macaroon",
"SATOSHIAPI_LND_CERT": "/path/to/tls.cert"
}
}
}
}
Tools (15 total)
| Tool | Cost | Description |
|---|---|---|
get_btc_price |
10 sats | BTC/USD + 24h change |
get_mempool_fees |
10 sats | Fee estimates (sat/vB) |
get_block_height |
10 sats | Block height + hashrate |
get_halving_info |
10 sats | Halving countdown + supply |
get_tx_info |
10 sats | Transaction details |
get_sentiment |
25 sats | Fear & Greed index |
get_fees_forecast |
25 sats | Optimal send timing |
get_lightning_stats |
25 sats | LN capacity + node stats |
get_address_info |
25 sats | Address balance + UTXOs |
get_dca_signal |
50 sats | STRONG_BUY/BUY/HOLD/REDUCE |
get_market_summary |
50 sats | Full market snapshot |
get_whale_activity |
100 sats | Large tx + exchange flows |
get_market_regime |
150 sats | Bull/bear/crab + confidence |
get_risk_score |
200 sats | Composite risk 0–100 |
get_dca_plan |
200 sats | Personalized DCA plan |
Links
- Live API: api.satoshiapi.io
- Source: github.com/SatoshiAPI/satoshi-btc-api (MIT)
- Node:
03176f9948d333f9cc1d7d409353f995816e44b3c90a3300b5a08ceba811faf989
Metadata
Release files for satoshiapi-mcp 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| satoshiapi_mcp-1.0.3.tar.gz | 5.4 kB | Without provenance | Details for satoshiapi_mcp-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| satoshiapi_mcp-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for satoshiapi_mcp-1.0.3-py3-none-any.whl |
Total release size: 11.3 kB
Release files / satoshiapi_mcp-1.0.3.tar.gz
| Download URL | satoshiapi_mcp-1.0.3.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3049c9f42469dac60d8b2b1a07e0fbf4549a2e7fa589a459d200059239e48405
|
|
BLAKE2b-256 checksum How to use checksums |
464de7e17fb36d698acda212565edf0511f7802fd622a2c265bcbe0134e3229c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / satoshiapi_mcp-1.0.3-py3-none-any.whl
| Download URL | satoshiapi_mcp-1.0.3-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e5c070c4cd0ec8c8ed56f94cdaec32b25944e2b11d1bb96fb5552cde49f7bec
|
|
BLAKE2b-256 checksum How to use checksums |
408fbf5480e4255c69d723eb6da17b5f0cd0eb4c30c8dac764a3c1de67085102
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for satoshiapi-mcp 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.