
SatoshiAPI — Bitcoin Data via Lightning
io.github.SatoshiAPIPublished by GitHub account SatoshiAPIv1.0.2Updated Oct 25, 2026
L402 Lightning-paid Bitcoin data: price, fees, blocks, sentiment, DCA signals.
The publisher's own server: SatoshiAPI — Bitcoin Intelligence via Lightning
Overview
A local MCP server that gives an assistant Bitcoin data — price, fees, blocks, sentiment and DCA signals — paid per request over Lightning L402.
- What you can do
- Retrieve Bitcoin market data such as price and fees through the assistant's tools, with results paid for per request over Lightning L402 rather than a subscription key. Fetch block information and sentiment indicators, and get DCA (dollar-cost averaging) signals. Payment is handled automatically through a connected LND node using the configured certificate, macaroon and REST endpoint.
- When to use it
- Use it when you want an assistant to pull Bitcoin price, fee, block, sentiment or DCA data and you already run an LND Lightning node that can pay L402 invoices automatically. It suits desktop setups where per-request Lightning payment is acceptable.
- Requirements
- Runs as a local Python package (satoshiapi-mcp) over stdio, desktop only. Needs a reachable LND node and three environment variables: SATOSHIAPI_LND_CERT (TLS certificate path), SATOSHIAPI_LND_MACAROON (invoice macaroon path) and SATOSHIAPI_LND_REST (LND REST endpoint). Network access to the data provider and to LND is required.
Installation
In SourceWeft
- Open SatoshiAPI — Bitcoin Data via Lightning in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.