🌐 Lightning Network MCP Server

Created By
AbdelStarka year ago
Ligthning Network MCP server.
Overview

What is Lightning Network MCP Server?

Lightning Network MCP Server is a Model Context Protocol (MCP) server that enables AI models to interact with the Lightning Network, allowing them to pay invoices.

How to use Lightning Network MCP Server?

To use the server, you can install it via Smithery or manually clone the repository, install dependencies, and configure the environment variables. Start the server in development or production mode to begin using its features.

Key features of Lightning Network MCP Server?

  • 📝 Pay invoices on the Lightning Network
  • 🤖 MCP-compliant API for AI integration

Use cases of Lightning Network MCP Server?

  1. Enabling AI models to make payments on the Lightning Network.
  2. Facilitating invoice payments for decentralized applications.
  3. Integrating with various AI services that require payment functionalities.

FAQ from Lightning Network MCP Server?

  • Can I use this server for any AI model?

Yes! The server is designed to be compatible with any AI model that can utilize the MCP protocol.

  • Is there a specific version of Node.js required?

Yes, Node.js version 18 or higher is required to run the server.

  • How can I contribute to the project?

You can fork the repository, create a feature branch, and submit a pull request with your changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AbdelStark
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago