Maximumsats MCP

🚀 Maximum Sats MCP Server

An MCP server designed for Bitcoin AI tools and Nostr Web of Trust scoring. It supports pay-per-use via Lightning L402.

🚀 Quick Start

The Maximum Sats MCP Server offers a unique solution for Bitcoin AI tools and Nostr Web of Trust scoring, with pay - per - use functionality through Lightning L402.

✨ Features

Why MaximumSats?

As MCP servers become more widespread, a crucial question arises: How can we secure and monetize MCP API access in a decentralized manner? MaximumSats provides the following:

• L402 Payment Endpoints — Every API call can require payment in satoshis.
• Web of Trust (WoT) Scoring — A Sybil - resistant reputation system for Nostr users.
• Nostr ID Utilities — Decoding/encoding of npub, note, nprofile, nevent, naddr, and more.

Use Cases

• Bounty Platforms — Pay hunters per task and prevent sybil attacks with WoT.
• AI Agent Marketplaces — Monetize MCP tools on a per - call basis.
• Data Feeds — Secure oracle data with L402.
• Reputation Systems — WoT - powered trust scoring.

📦 Installation

You can install the server using the following command:

npx maximumsats-mcp

Or add it to your MCP client config:

{
  "mcpServers": {
    "maximumsats": {
      "command": "npx",
      "args": ["maximumsats-mcp"]
    }
  }
}

💻 Usage Examples

Tools

AI Tools (maximumsats.com)

Web of Trust (wot.klabo.world) — 50 free/day

Quick Examples

Get Started: One Payment, One Retry L402 Flow

The MaximumSats API uses L402. Here's 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":{...}}

Check a user's reputation before paying a bounty

curl -s "https://wot.klabo.world/score/npub1..." | jq '.score'
# Returns: {"score": 42, "rank": 1234, "percentile": 95.5}

Decode a Lightning invoice before payment

curl -X POST "https://maximumsats.com/api/bolt11-decode" \
  -H "Content-Type: application/json" \
  -d '{"invoice":"lnbc..."}'
# Returns: amount, description_hash, expiry, payee pubkey

Verify a Nostr identity (NIP - 05)

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

🔧 Technical Details

Security & Governance Features

MaximumSats is designed 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 as follows:

# 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":{...}}

2. Sybil Resistance with WoT

The WoT endpoint scores Nostr pubkeys based on their network position, which is valuable for:

• Bounty platforms preventing fake accounts.
• Voting systems needing sybil resistance.
• Reputation engines.

curl https://maximumsats.com/api/wot/npub1...
# Returns: {"score": 45, "rank": 1234, "percentile": 95.5}

3. No Middleman — Direct Lightning

• Instant settlement on the Lightning Network.
• No subscriptions, pay per request.
• Pseudonymous, no KYC required.

Technical Implementation

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 the Lightning Network, avoiding blockchain bloat.

📚 Documentation

• maximumsats.com/stats — AI tools pricing.
• wot.klabo.world/docs — WoT API interactive docs.
• wot.klabo.world/openapi.json — OpenAPI 3.0 spec.

📄 License

MIT