Liveauth MCP Server

MCP server for LiveAuth: PoW + Lightning auth, L402 bundles, and paid MCP tool receipts. That is what the liveauth mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

This MCP server lets any AI agent authenticate against your API using proof-of-work (free, no account) or Lightning Network micropayments (sats), then meter and monetize subsequent tool calls with per-call pricing, idempotent revenue events, and HMAC-signed receipts that auditors can verify offline.

• Stop bots at the protocol layer. PoW and Lightning sats are non-replayable, non-phishable, and don't require user accounts
• Charge per call in sats. We sign a receipt you can show auditors, your customers, or your accountant
• Wrap any MCP tool with one line (createMcpGate) and you get per-tool revenue, per-tool min/max pricing, and idempotent retries
• Permissionless access to paid APIs — solve a PoW or pay sats, get a JWT. No signup, no email, no OAuth dance
• Use PoW, Lightning invoices, or L402 bundle macaroons for agent access
• Projects can settle through a custom Lightning node when configured; otherwise payments use the LiveAuthCore-configured node

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 7 tools. What each one is for:

• liveauth_mcp_start — Begin a session. Returns a PoW challenge, a Lightning invoice, or an L402 bundle hint
• liveauth_mcp_confirm — Submit a solved PoW challenge, a paid Lightning invoice, or an L402 macaroon → receive a JWT
• liveauth_mcp_charge — Meter usage after a call. With toolName, resolves registered tool pricing and records a paid revenue event
• liveauth_mcp_refresh — Exchange a refresh token for a new JWT — no re-auth required
• liveauth_mcp_status — Poll session/payment status (Lightning confirmation, expiry)
• liveauth_mcp_lnurl — Fetch the BOLT11 invoice for a session (lnget-compatible)
• liveauth_mcp_usage — Query remaining budget, calls used, and rate-limit windows

What it needs from you

Configuration is passed through the environment: LIVEAUTH_API_BASE, LIVEAUTH_API_KEY, LIVEAUTH_PUBLIC_KEY, LIVEAUTH_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Liveauth's toolset — liveauth_mcp_start, liveauth_mcp_confirm, liveauth_mcp_charge and 4 more — is a fair guide to whether it matches your workflow. It is maintained by dulzuradev; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.