This server wires up Bitcoin and Lightning Network tools with native L402 micropayment gating. You get AI endpoints like ask_bitcoin and generate_image that charge per request in satoshis, plus a full suite of Nostr Web of Trust scoring tools for reputation checks and sybil detection. Every API call can require Lightning payment via the L402 protocol: you hit an endpoint, get a 402 with an invoice, pay it, then retry with the payment hash. The WoT endpoints are free up to 50 calls per day and cover scoring, trust paths, network analysis, and anomaly detection across 51,000+ Nostr nodes. Reach for this when you need pay-per-use APIs or reputation gating without subscriptions or middlemen.
MCP server for Bitcoin AI tools and Nostr Web of Trust scoring. Pay-per-use via Lightning L402.
As MCP servers proliferate, a critical question emerges: How do we secure and monetize MCP API access in a decentralized way?
MaximumSats delivers:
npx maximumsats-mcp
Or add to your MCP client config:
{
"mcpServers": {
"maximumsats": {
"command": "npx",
"args": ["maximumsats-mcp"]
}
}
}
| Tool | Cost | Description |
|---|---|---|
ask_bitcoin | 21 sats | Ask about Bitcoin/Lightning (Llama 3.3 70B) |
generate_image | 100 sats | Text-to-image (FLUX.1 Schnell 12B) |
| Tool | Description |
|---|---|
wot_score | PageRank trust score (0-100) with rank and percentile |
wot_sybil_check | 5-signal Sybil detection (genuine/suspicious/likely_sybil) |
wot_trust_path | Hop-by-hop trust path between two pubkeys |
wot_network_health | Network metrics: 51K+ nodes, Gini coefficient, density |
wot_follow_quality | Follow list quality analysis with suggestions |
wot_trust_circle | Mutual follows with trust strength and cohesion |
wot_anomalies | Ghost followers, asymmetric patterns, cluster detection |
wot_predict_link | Link prediction (5 topology signals) |
wot_compare_providers | Cross-provider NIP-85 trust score consensus |
wot_influence | Simulate follow/unfollow ripple effects |
MaximumSats is purpose-built for the Secure & Govern MCP track:
Every endpoint can be gated behind payment. The L402 flow is simple:
# Request returns HTTP 402 with Lightning invoice
curl -X POST https://maximumsats.com/api/dvm \
-H "Content-Type: application/json" \
-d '{"prompt":"hello"}'
# Returns: {"error":"Payment required","payment_request":"lnbc21...","payment_hash":"abc123","amount_sats":21}
# Pay the invoice in your Lightning wallet, then retry with payment_hash in Authorization header:
curl -X POST https://maximumsats.com/api/dvm \
-H "Content-Type: application/json" \
-H "Authorization: abc123" \
-d '{"prompt":"hello"}'
# Returns: {"status":"success","data":{...}}
The WoT endpoint scores Nostr pubkeys based on their network position — valuable for:
curl https://maximumsats.com/api/wot/npub1...
# Returns: {"score": 45, "rank": 1234, "percentile": 95.5}
MaximumSats uses the L402 protocol (Lightning HTTP 402):
// Challenge response includes invoice
{ status: 402, error: "Payment required", invoice: "lnbc...", amount_sats: 21 }
// After payment, include payment_hash in retry
{ status: 402, error: "Payment required", payment_hash: "abc123..." }
// Successful response after payment verification
{ status: 200, data: { ... } }
All payment flows through Lightning Network — no blockchain bloat.
The MaximumSats API uses L402 — here's exactly how to pay and get results:
# Step 1: Request (returns 402 with Lightning invoice)
curl -X POST "https://maximumsats.com/api/bolt11-decode" \
-H "Content-Type: application/json" \
-d '{"invoice":"lnbc1..."}'
# Response: {"error":"Payment required","payment_request":"lnbc...","payment_hash":"abc123...","amount_sats":21}
# Step 2: Pay the invoice in your Lightning wallet, then retry with payment_hash:
curl -X POST "https://maximumsats.com/api/bolt11-decode" \
-H "Content-Type: application/json" \
-H "Authorization: abc123..." \
-d '{"invoice":"lnbc1..."}'
# Response: {"status":"success","data":{...}}
curl -s "https://wot.klabo.world/score/npub1..." | jq '.score'
# Returns: {"score": 42, "rank": 1234, "percentile": 95.5}
curl -X POST "https://maximumsats.com/api/bolt11-decode" \
-H "Content-Type: application/json" \
-d '{"invoice":"lnbc..."}'
# Returns: amount, description_hash, expiry, payee pubkey
curl -X POST "https://maximumsats.com/api/nip05-verify" \
-H "Content-Type: application/json" \
-d '{"identifier":"bob@nostr.com"}'
# Returns: pubkey, valid boolean, relay hints
MIT