
Maximum Sats
io.github.joelklaboPublished by GitHub account joelklabov1.0.0Updated Oct 24, 2026
Bitcoin & Lightning Network AI tools with native Lightning L402 micropayments.
Overview
A local MCP server giving assistants Bitcoin and Lightning AI tools plus Nostr Web of Trust reputation scoring, with pay-per-call Lightning L402 payments.
- What you can do
- Exposes Bitcoin and Lightning AI tools such as ask_bitcoin (a language-model Q&A endpoint) and generate_image (text-to-image), each priced in satoshis and gated behind Lightning L402 payment. It also provides Nostr Web of Trust tools: trust scores, Sybil detection, trust paths, network health metrics, follow-list quality, trust circles, anomaly detection, link prediction, cross-provider score comparison, and influence simulation. A free daily quota applies to the Web of Trust endpoints.
- When to use it
- Useful when an assistant needs Bitcoin or Lightning answers, generated images, or Nostr reputation and Sybil-resistance checks, for example screening accounts before paying bounties or assessing trust between pubkeys. It is aimed at pay-per-call access rather than subscription-based API use.
- Requirements
- Runs as a local process via npx (Node.js required). Network access to maximumsats.com and wot.klabo.world. Paid tools require a Lightning wallet to pay the returned invoice and a retry carrying the payment hash in the Authorization header. No environment variables or headers are declared in the manifest.
Installation
In SourceWeft
- Open Maximum Sats 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
Maximum Sats MCP Server
MCP server for Bitcoin AI tools and Nostr Web of Trust scoring. Pay-per-use via Lightning L402.
Why MaximumSats?
As MCP servers proliferate, a critical question emerges: How do we secure and monetize MCP API access in a decentralized way?
MaximumSats delivers:
- L402 Payment Endpoints — Every API call can require payment in satoshis
- Web of Trust (WoT) Scoring — Sybil-resistant reputation for Nostr users
- Nostr ID Utilities — Decoding/encoding npub, note, nprofile, nevent, naddr, and more
Use Cases
- Bounty Platforms — Pay hunters per task, prevent sybil with WoT
- AI Agent Marketplaces — Monetize MCP tools per-call
- Data Feeds — Secure oracle data with L402
- Reputation Systems — WoT-powered trust scoring
Install
Or add to your MCP client config:
Tools
AI Tools (maximumsats.com)
Web of Trust (wot.klabo.world) — 50 free/day
Security & Governance Features
MaximumSats is purpose-built for the Secure & Govern MCP track:
1. Paid API Access Control — One Payment, One Retry
Every endpoint can be gated behind payment. The L402 flow is simple:
2. Sybil Resistance with WoT
The WoT endpoint scores Nostr pubkeys based on their network position — valuable for:
- Bounty platforms preventing fake accounts
- Voting systems needing sybil resistance
- Reputation engines
3. No Middleman — Direct Lightning
- Instant settlement on Lightning Network
- No subscriptions, pay per request
- Pseudonymous, no KYC required
Technical Implementation
MaximumSats uses the L402 protocol (Lightning HTTP 402):
All payment flows through Lightning Network — no blockchain bloat.
APIs
- maximumsats.com/stats — AI tools pricing
- wot.klabo.world/docs — WoT API interactive docs
- wot.klabo.world/openapi.json — OpenAPI 3.0 spec
Quick Examples
Get Started: One Payment, One Retry L402 Flow
The MaximumSats API uses L402 — here's exactly how to pay and get results:
Check a user's reputation before paying a bounty
Decode a Lightning invoice before payment
Verify a Nostr identity (NIP-05)
License
MIT
Source: README.md at commit b974195
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% 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
- License10 pts