maximumsats-mcp
Bitcoin Lightning + Nostr Web-of-Trust tools for agents (L402 pay-per-call endpoints)
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
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
- 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:
# 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":"[email protected]"}'
# Returns: pubkey, valid boolean, relay hints
License
MIT
Serveurs connexes
Alpha Vantage MCP Server
sponsorAccess financial market data: realtime & historical stock, ETF, options, forex, crypto, commodities, fundamentals, technical indicators, & more
Drupal Modules MCP
Retrieve detailed information about Drupal modules from drupal.org, including version compatibility, installation instructions, and documentation.
TeamCity MCP Server
MCP server for JetBrains TeamCity with 87 tools for builds, tests, agents, and CI/CD pipeline management.
AST2LLM for Go
A local AST-powered context enhancement tool for LLMs that analyzes Go project structure for faster context resolution.
Tabby-MCP-Server
A Tabby plugin implementing an MCP server for AI-powered terminal control and automation.
DocsetMCP
A server for accessing Dash-style documentation sets locally. Requires a local Dash installation.
Pistachio MobileDev MCP
Android + iOS development for non-technical users
LastSaaS
SaaS boilerplate / starter kit: comprehensive, Stripe billing, product management, multi-tenant; agentic controls via MCP
mcp-graphql
A GraphQL server that supports the Model Context Protocol (MCP), enabling Large Language Models (LLMs) to interact with GraphQL APIs through schema introspection and query execution.
BCMS MCP
Give me a one - two sentence description of the BCMS MCP # MCP The BCMS Model Context Protocol (MCP) integration enables AI assistants like Claude, Cursor, and other MCP-compatible tools to interact directly with your BCMS content. This allows you to create, read, and update content entries, manage media files, and explore your content structure—all through natural language conversations with AI. ## What is MCP? The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) is an open standard developed by Anthropic that allows AI applications to securely connect to external data sources and tools. With BCMS MCP support, you can leverage AI assistants to: - Query and explore your content structure - Create new content entries with AI-generated content - Update existing entries - Manage your media library - Get intelligent suggestions based on your content model --- ## Getting Started ### Prerequisites 1. A BCMS account with an active instance 2. An MCP key with appropriate permissions 3. An MCP-compatible client (Claude Desktop, Cursor, or any MCP client) ### Step 1: Create an MCP Key 1. Navigate to your BCMS dashboard 2. Go to Settings → MCP 3. Click Create MCP Key 4. Configure the permissions for templates you want the AI to access:GET: Read entries 5. POST: Create entries 6. PUT: Update entries 7. DELETE: Delete entries Note: Right now, MCP only supports creating, reading and updating content. ### Step 2: Configure Your MCP Client You can find full instructions for integrating BCMS with your AI tools right inside BCMS, on the MCP page. But in general, installing BCMS MCP works in a standard way: ``` { "mcpServers": { "bcms": { "url": "https://app.thebcms.com/api/v3/mcp?mcpKey=YOUR_MCP_KEY" } } } ``` ## Available Tools Once connected, your AI assistant will have access to the following tools based on your MCP key permissions: ### Content Discovery #### list_templates_and_entries Lists all templates and their entries that you have access to. This is typically the first tool to call when exploring your BCMS content. Returns: - Template IDs, names, and slugs - Entry IDs with titles and slugs for each language Example prompt: "Show me all the templates and entries in my BCMS" --- ### Entry Management #### list_entries_for_{templateId} Retrieves all entries for a specific template with full content data. A separate tool is generated for each template you have access to. Returns: - Complete entry data including all meta fields - Content in all configured languages - Entry statuses Example prompt: "List all blog posts from my Blog template" --- #### create_entry_for_{templateId} Creates a new entry for a specific template. The input schema is dynamically generated based on your template's field structure. Input: - statuses: Array of status assignments per language - meta: Array of metadata for each language (title, slug, custom fields) - content: Array of content nodes for each language Example prompt: "Create a new blog post titled 'Getting Started with BCMS' with a brief introduction paragraph" --- #### update_entry_for_{templateId} Updates an existing entry for a specific language. Input: - entryId: The ID of the entry to update - lng: Language code (e.g., "en") - status: Optional status ID - meta: Updated metadata - content: Updated content nodes Example prompt: "Update the introduction paragraph of my 'Getting Started' blog post" --- ### Media Management #### list_all_media Lists all media files in your media library. Returns: - Media IDs, names, and types - File metadata (size, dimensions for images) - Parent directory information Example prompt: "Show me all images in my media library" --- #### list_media_dirs Lists the directory structure of your media library. Returns: - Hierarchical directory structure - Directory IDs and names Example prompt: "Show me the folder structure of my media library" --- #### create-media-directory Creates a new directory in your media library. Input: - name: Name of the directory - parentId: Optional parent directory ID (root if not specified) Example prompt: "Create a new folder called 'Blog Images' in my media library" --- #### request-upload-media-url Returns a URL you use to upload a file (for example via POST with multipart form data), which avoids pushing large binaries through the MCP tool payload. You still need a valid file name and MIME type when uploading, as described in the tool response. Availability: Only when the MCP key has Can mutate media enabled. Example prompt: “Give me an upload URL for a new hero image, then tell me how to upload it.” Input: - fileName: Name of the file with extension - fileData: Base64-encoded file data (with data URI prefix) - parentId: Optional parent directory ID Example prompt: "Upload this image to my Blog Images folder" --- ### Linking Tools #### get_entry_pointer_link Generates an internal BCMS link to an entry for use in content. Input: - entryId: The ID of the entry to link to Returns: - Internal link format: entry:{entryId}@*_{templateId}:entry Example prompt: "Get me the internal link for the 'About Us' page entry" --- #### get_media_pointer_link Generates an internal BCMS link to a media item for use in content. Input: - mediaId: The ID of the media item Returns: - Internal link format: media:{mediaId}@*_@*_:entry Example prompt: "Get the link for the hero image so I can use it in my blog post" --- ## Content Structure ### Entry Content Nodes When creating or updating entries, content is structured as an array of nodes. Supported node types include: Type Description paragraph Standard text paragraph heading Heading (h1-h6) bulletList Unordered list orderedList Numbered list listItem List item codeBlock Code block with syntax highlighting blockquote Quote block image Image node widget Custom widget with props ### Example Content Structure ``` { "content": [ { "lng": "en", "nodes": [ { "type": "heading", "attrs": { "level": 1 }, "content": [ { "type": "text", "text": "Welcome to BCMS" } ] }, { "type": "paragraph", "content": [ { "type": "text", "text": "This is your first paragraph." } ] } ] } ] } ``` ## Security & Permissions ### MCP Key Scopes Your MCP key controls what the AI can access: - Template Access: Only templates explicitly granted in the MCP key are visible - Operation Permissions: Each template can have independent GET/POST/PUT/DELETE permissions - Media Access: Media operations are controlled separately ### Best Practices 1. Principle of Least Privilege: Only grant the permissions needed for your use case 2. Separate Keys: Create different MCP keys for different purposes or team members 3. Regular Rotation: Periodically rotate your MCP keys ## Use Cases ### Content Creation Workflows Blog Post Creation "Create a new blog post about the benefits of headless CMS. Include an introduction, three main benefits with explanations, and a conclusion. Use the Blog template." Product Updates "Update the price field for all products in the Electronics category to apply a 10% discount" ### Content Exploration Content Audit "List all blog posts that don't have a featured image set" Translation Status "Show me which entries are missing German translations" ### Media Organization Library Cleanup "Show me all unused images in the media library" Folder Setup "Create folder structure for: Products > Categories > Electronics, Clothing, Home" ## Troubleshooting ### Common Issues #### "MCP key not found" - Verify your MCP key format: keyId.keySecret.instanceId - Ensure the MCP key hasn't been deleted or deactivated - Check that you're using the correct instance #### "MCP key does not have access to template" - Review your MCP key permissions in the dashboard - Ensure the required operation (GET/POST/PUT/DELETE) is enabled for the template #### Session Expired - MCP sessions may timeout after periods of inactivity - Simply start a new conversation to establish a fresh session ### Getting Help - Documentation: [thebcms.com/docs](https://thebcms.com/docs) - Support: [[email protected]](mailto:[email protected]) - Community: [Join BCMS Discord](https://discord.com/invite/SYBY89ccaR) for community support ## Technical Reference ### Endpoint POST https://app.thebcms.com/api/v3/mcp?mcpKey={MCP_KEY} ### Transport BCMS MCP uses the Streamable HTTP transport with session management. Sessions are maintained via the mcp-session-id header. ### Response Format All tools return structured JSON responses conforming to the MCP specification with: - content: Array of content blocks - structuredContent: Typed response data ## Rate Limits MCP requests are subject to the same rate limits as API requests: - Requests are tracked per MCP key - Contact support if you need higher limits for production workloads
MCP Hot-Reload
A Hot Module Replacement (HMR) proxy server for MCP servers that automatically restarts on file changes, buffers messages, and manages connections.