402-mcp@3.15.2
VERIFIED· not startedPublisher claims: "AI agents discover, pay for, and consume any Lightning-gated API autonomously" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
CASHU_TOKENSCREDENTIAL_STORENODE_TLS_REJECT_UNAUTHORIZEDConfiguration, not credentials: ALLOW_INSECURE_TLS, BIND_ADDRESS, CORS_ORIGIN, FALLBACK_KEY_PATH, FETCH_MAX_RESPONSE_BYTES, FETCH_MAX_RETRIES, FETCH_TIMEOUT_MS, HNS_GATEWAY_URL, HUMAN_PAY_POLL_S, HUMAN_PAY_TIMEOUT_S, MAX_AUTO_PAY_SATS, MAX_SPEND_PER_MINUTE_SATS, NWC_URI, SOCKS_PROXY, SSRF_ALLOW_PRIVATE, TOR_PROXY, TRANSPORT, TRANSPORT_PREFERENCE- Where it talks to
- no vendor host named in the codeAlso hdns.io — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names hdns.io as well as its own vendor. The guard injects CASHU_TOKENS, CREDENTIAL_STORE, NODE_TLS_REJECT_UNAUTHORIZED only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-20 and scored it 84/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 20 s · 2 scenarios · 0 deviationsStatic findings
catch { /* stat/chmod may fail on some platforms — proceed with read */ }Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.// For ERC-20 tokens (not native ETH), use the transfer function call formatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.<summary>Full comparison</summary> | | 402-mcp | Lightning Labs agent tools | |---|---|---| | **Payment rails** | NWC + Cashu + human fallback | Lightning only Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for 402-mcp@3.15.2 as of 47 min ago. This is the package itself, not its dependencies.