MCP.so
ログイン

Liveauth Mcp Server

@dulzuradev

Liveauth Mcp Server について

LiveAuth MCP Server gives AI agents cryptographic proof-of-work + Lightning

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

dulzuradev

投稿者

Dulzura Dev

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "liveauth": {
      "command": "npx",
      "args": [
        "-y",
        "@liveauth-labs/mcp-server"
      ],
      "env": {
        "LIVEAUTH_API_KEY": "la_pk_xxx"
      }
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Liveauth Mcp Server?

Liveauth Mcp Server is an MCP server that provides authentication, pay-per-call metering, and signed receipts for AI agents and MCP tools. It uses proof-of-work (free, no account) or Lightning Network micropayments (sats) to gate API access, then meters and monetizes subsequent tool calls with per-call pricing and HMAC-signed receipts. It is designed for API providers and agent builders who want to stop bots, charge per call, and issue a tamper-evident audit trail.

How to use Liveauth Mcp Server?

You can run Liveauth Mcp Server in demo mode (no account) with npx @liveauth-labs/mcp-server. For production, set the LIVEAUTH_API_KEY environment variable and add it to your MCP client configuration (e.g., Claude Desktop’s claude_desktop_config.json). It also provides a TypeScript SDK for programmatic use, with helper functions like createMcpClient and createMcpGate.

Key features of Liveauth Mcp Server

  • Proof-of-work and Lightning Network authentication (no accounts required)
  • Per-call metering with configurable pricing in sats
  • HMAC-SHA256 signed receipts (mcp-call-receipt-v1) for every paid invocation
  • idempotent revenue events with retry-safe keys
  • L402 bundle support for prepaid MCP sessions

Use cases of Liveauth Mcp Server

  • Stop bot scraping at the protocol layer using cost-of-attack economics
  • Allow AI agents to access paid APIs without signup or OAuth
  • Issue a verifiable audit trail for every paid tool call
  • Offer Lightning-backed L402 bundles for prepaid MCP access

FAQ from Liveauth Mcp Server

What is the difference between demo and production mode?

Demo mode returns a real Lightning invoice but simulates payment confirmation, so you can test the flow without an account. Production mode requires a LiveAuth API key and confirms payments against the LiveAuth backend.

What authentication methods does it support?

It supports proof-of-work (PoW) challenges, Lightning Network invoices (BOLT11), and L402 bundle macaroons.

How do signed receipts work?

Each paid tool invocation returns an HMAC-SHA256 signed receipt with a revenue event ID, sats amounts, and metadata. Receipts can be stored with tool results for later auditing or reconciliation.

What are the runtime dependencies?

Liveauth Mcp Server requires Node.js and runs via npx or as an installed npm package. It communicates with api.liveauth.app over HTTPS and assumes your MCP client supports stdio (JSON‑RPC 2.0).

Can it be used with other MCP clients besides Claude Desktop?

Yes, it works with any MCP-compatible client (Cursor, VS Code, ChatGPT, Windsurf, Continue, Cline) that supports stdio transport.

コメント

「その他」の他のコンテンツ