MCP server for Lexe Lightning. Provides tools for creating Lightning invoices and paying Lightning offers/invoices through the Lexe gateway.
Server implements 9 Lightning payment tools with HTTP transport and basic schema definitions. Tool names follow verb_noun convention (create_invoice, pay_invoice, etc.), which is good. However, parameter descriptions are minimal (10-30 chars), falling well below the 72-char baseline for production tools. Input schemas are present but sparse, most parameters lack type constraints, enums, or validation guidance. Output schemas are not documented. Error handling is absent from tool definitions. The server handles sensitive credentials (Lexe SDK tokens) via Authorization header injection, which is correct, but tool descriptions do not explain prerequisites or when to use each tool vs. alternatives.
Analyze and classify a payment string (invoice, offer, address, etc.)
Create a Lightning invoice for receiving payments
Create a BOLT12 offer for receiving payments
Create a payer proof for a payment
Get information about the user's Lightning node
Get the status of a payment by ID
List recent payments
Pay a Lightning invoice
Parameter descriptions are too brief (10-30 chars vs. 72-char baseline). LLMs cannot infer meaning from names alone, 'amount' could be satoshis, millisatoshis, or fiat; 'note' is vague about length/format constraints.
No output schemas documented. LLMs cannot plan downstream calls or extract required fields (e.g., does list_payments return payment_id, amount, timestamp?). Breaks tool chaining.
No error handling guidance in tool definitions. If pay_invoice fails (insufficient balance, invalid BOLT11, network error), LLM has no recovery path. Missing pattern:recovery-guide.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2026-07-28+ | v2 |
Pay a BOLT12 offer
Tool descriptions lack context on when to use each tool. 'Create a Lightning invoice' vs 'Create a BOLT12 offer', LLM cannot infer the difference without domain knowledge. Missing dependency hints.
No input validation constraints visible. 'amount' parameter accepts string but no min/max satoshi bounds, no format validation. 'start_index' in list_payments has no pagination guidance (limit, total_count).