Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.donovanh/mcp-server

NPM · @LIGHTNING-TOOLS/MCP-SERVER · SCANNED AUG 3

MCP server for Lightning Tools — pay-per-call AI tools via Bitcoin Lightning

+42 this week 61 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 172 tokens (~43/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @lightning-tools/mcp-server

# add to Claude Code
claude mcp add donovanh-mcp-server -- npx -y @lightning-tools/mcp-server
# add to Codex CLI
codex mcp add donovanh-mcp-server -- npx -y @lightning-tools/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "donovanh-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@lightning-tools/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add donovanh-mcp-server --command npx --arg -y --arg @lightning-tools/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  donovanh-mcp-server:
    command: "npx"
    args: ["-y", "@lightning-tools/mcp-server"]
// mcp.json
{
  "mcpServers": {
    "donovanh-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@lightning-tools/mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +60
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • License: unverified → fail functional
    • MCP protocol: unverified → pass functional
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Tool coverage: unverified → 100 functional
    • Stability: unverified → 0.23 functional
  • 31 Jul 26 −33
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −36
    • Known CVEs: partial → unverified security
    • Malware scan: pass → unverified security
    • Provenance: fail → unverified security
    • Install scripts: pass → unverified security
    • Dependency health: partial → unverified functional
    • License: fail → unverified functional
    • Maintenance: pass → unverified functional
  • 28 Jul 26 +50
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • License: unverified → fail functional
    • Maintenance: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: good functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: fail functional
  • 27 Jul 26 19

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@lightning-tools/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 4 exposed · ~172 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
buy_credits ~51

Purchase Lightning Tools credits via Bitcoin Lightning invoice. Costs N sats = N credits. Also unlocks all service tools once paid.

NameTypeReqDescription
quantityintegeryesNumber of credits to purchase (minimum 1000)

No output schema declared.

No examples provided.

check_balance ~19

Return the current credit balance for your active API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_api_key ~45

Store an existing Lightning Tools API key. Saves it to config and unlocks all service tools.

NameTypeReqDescription
apiKeystringyesYour Lightning Tools API key (starts with sk_)

No output schema declared.

No examples provided.

verify_payment ~57

Confirm a Lightning payment and receive your API key. Call after paying the invoice from buy_credits.

NameTypeReqDescription
invoiceIdstringyesInvoice ID returned by buy_credits
quantityintegeryesMust match quantity from buy_credits

No output schema declared.

No examples provided.