LiveAuth MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIVEAUTH_DEMO | No | Force demo mode even with a key set. | false |
| LIVEAUTH_API_KEY | No | Your LiveAuth project public key (la_pk_…). | |
| LIVEAUTH_API_BASE | No | Override for self-hosted LiveAuth. | https://api.liveauth.app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| liveauth_mcp_startA | Start a new LiveAuth MCP session. Returns a PoW challenge (default), Lightning invoice, or L402 bundle auth hint. |
| liveauth_mcp_statusA | Check the status of an MCP session. Use to poll for Lightning payment confirmation. Also returns the invoice via lnurl compatibility. |
| liveauth_mcp_lnurlB | Get the Lightning invoice for a session (lnget-compatible). Use this to retrieve the BOLT11 invoice for payment. |
| liveauth_mcp_confirmA | Submit the solved proof-of-work challenge (or poll for Lightning payment) to receive a JWT. For Lightning, call with just quoteId to check/poll payment status. |
| liveauth_mcp_chargeA | Meter API usage after making an authenticated call. Call this with the cost in sats for each API request made using the JWT. |
| liveauth_mcp_usageA | Query current usage and remaining budget for the MCP session. Use this to check how many sats and calls have been used without making a charge. |
| liveauth_mcp_refreshA | Refresh the JWT token without re-authenticating. Use the refreshToken returned from confirm to get a new JWT. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a distinct auth lifecycle step: start initiates, lnurl fetches invoice, confirm resolves auth, refresh renews token, charge/usage handle metering, and status reports state. Slight overlap exists between status and confirm when polling payment, but descriptions clarify their primary roles.
All tools share the consistent liveauth_mcp_ prefix and snake_case format. Most use verbs (start, confirm, refresh, charge), but status, usage, and lnurl are noun-based, creating minor deviations from a strict verb pattern.
With 7 tools, the set is well-scoped for the server's purpose. Each tool covers a specific function without redundancy, fitting comfortably in the ideal 3-15 tool range.
The toolset provides full lifecycle coverage: starting a session, retrieving invoices, confirming authentication, refreshing tokens, and tracking/metering usage. No significant operational gaps are apparent for the stated authentication and payment domain.