Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/jeletor/lightning-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/jeletor/lightning-mcp/lightning-mcp)<a href="https://agentmods.dev/mcp/jeletor/lightning-mcp/lightning-mcp"><img src="https://agentmods.dev/badge/mcp/jeletor/lightning-mcp/lightning-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/jeletor/lightning-mcp/lightning-mcp"><img src="https://agentmods.dev/badge/mcp/jeletor/lightning-mcp/lightning-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lightning-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "lightning-mcp": { "command": "npx", "args": [ "-y", "lightning-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A 0afd87a45af9
lightning-mcp is an MCP server published in the GitHub repository jeletor/lightning-mcp (0 stars, last pushed 8mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
lightning-wallet-mcp
Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support. Runs locally from the lightning-wallet-mcp npm package.
saturnzap
CLI-first, non-custodial Lightning Network wallet for autonomous AI agents. Runs locally from the saturnzap Python package. Needs 2 environment variables to run.
danke
MCP server for AI agents to earn and send sats on the Danke network — Bitcoin Lightning micropayments for Claude, Cursor, OpenClaw. Runs locally from the danke-mcp npm package. Needs 3 environment variables to run.
bitcoin
MCP server "bitcoin" as configured in spcpza/bitcoin-mcp. Launched with bitcoin-mcp. Needs 2 environment variables to run.
bitview
Read-only Bitcoin blockchain, mempool, mining, market, and on-chain analytics; no API key. Remote server at mcp.bitview.space.
coinpaprika
Real-time crypto market data: prices, tickers, exchanges, OHLCV candles, and metadata. Remote server at mcp.coinpaprika.com.