Skip to main content
Glama

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

Related MCP server: AgentBTC MCP Server

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

npx maximumsats-mcp

Or add to your MCP client config:

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

Tools

AI Tools (maximumsats.com)

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)

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

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

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:

# 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 — 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 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 Lightning Network — no blockchain bloat.

APIs

Quick Examples

Get Started: One Payment, One Retry L402 Flow

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

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

License

MIT

Available Tools

12 tools
ask_bitcoinA

Ask a question about Bitcoin, Lightning Network, or cryptocurrency. Powered by Llama 3.3 70B. Costs 21 sats via Lightning L402.

Inputs: prompt (required), payment_hash.

generate_imageA

Generate an image from a text prompt using FLUX.1 Schnell (12B). Costs 100 sats via Lightning L402.

Inputs: prompt (required), payment_hash.

wot_anomaliesA

Detect anomalous patterns in a Nostr pubkey's network behavior. Checks for ghost followers, asymmetric relationships, cluster patterns, and suspicious activity.

Inputs: pubkey (required), payment_hash.

wot_compare_providersB

Compare trust scores for a pubkey across multiple NIP-85 providers. Shows consensus classification and provider agreement.

Inputs: pubkey (required), payment_hash.

wot_follow_qualityA

Analyze the quality of a Nostr pubkey's follow list. Returns quality score, ghost follower ratio, diversity entropy, and improvement suggestions.

Inputs: pubkey (required), payment_hash.

wot_influenceA

Simulate what happens if one pubkey follows/unfollows another. Shows ripple effect across the network using differential PageRank.

Inputs: pubkey (required), other (required), action, payment_hash.

wot_network_healthA

Get Nostr network health metrics: node count, edge count, Gini coefficient (decentralization), power-law exponent, density, and component analysis. No pubkey needed.

Inputs: payment_hash.

wot_scoreA

Look up a Nostr pubkey's Web of Trust score (PageRank-based, 0-100). Returns score, rank, percentile, followers. 50 free requests/day, then L402.

Inputs: pubkey (required), payment_hash.

wot_sybil_checkA

Run 5-signal Sybil detection on a Nostr pubkey. Analyzes follower quality, mutual trust ratio, follow diversity, temporal patterns, and community integration. Returns classification: genuine, likely_genuine, suspicious, or likely_sybil.

Inputs: pubkey (required), payment_hash.

wot_trust_circleA

Get a pubkey's trust circle (mutual follows with trust strength). Returns members with roles, cohesion, and density metrics.

Inputs: pubkey (required), payment_hash.

wot_trust_pathA

Find the trust path between two Nostr pubkeys. Shows hop-by-hop path with trust scores at each hop. Useful for 'how am I connected to this person?'

Inputs: from (required), to (required), payment_hash.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 12 tools

    Disambiguation4/5

    The tools are mostly distinct with clear purposes, but there is some overlap in the Web of Trust (WoT) analysis tools. For example, wot_anomalies and wot_sybil_check both detect suspicious activity, which could cause confusion. However, each tool's description helps differentiate them by focusing on specific aspects like network patterns versus Sybil detection signals.

    Naming Consistency5/5

    The naming follows a highly consistent pattern. All Web of Trust tools use the 'wot_' prefix followed by a descriptive action or concept (e.g., wot_score, wot_trust_path). The non-WoT tools (ask_bitcoin, generate_image) also use clear verb_noun or action_object formats, maintaining overall consistency without mixing conventions.

    Tool Count5/5

    With 12 tools, the count is well-scoped for the server's purpose of providing Bitcoin/Lightning and Nostr Web of Trust services. It covers a broad range of functionalities without being overwhelming, with 2 tools for general Bitcoin tasks and 10 dedicated to WoT analysis, each serving a distinct role in the ecosystem.

    Completeness4/5

    The tool set offers comprehensive coverage for Nostr Web of Trust analysis, including scoring, network health, trust paths, and anomaly detection. Minor gaps exist, such as no direct tools for modifying or managing trust relationships (e.g., follow/unfollow actions), but agents can likely work around this given the strong analytical focus.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers