MCP server for LiveAuth: PoW + Lightning auth, L402 bundles, and paid MCP tool receipts.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
liveauth_mcp_startNo description publishedThis tool published no description. Forge does not invent one.
liveauth_mcp_statusNo description publishedThis tool published no description. Forge does not invent one.
liveauth_mcp_lnurlNo description publishedThis tool published no description. Forge does not invent one.
liveauth_mcp_confirmNo description publishedThis tool published no description. Forge does not invent one.
liveauth_mcp_chargeNo description publishedThis tool published no description. Forge does not invent one.
liveauth_mcp_usageNo description publishedThis tool published no description. Forge does not invent one.
liveauth_mcp_refreshNo description publishedThis tool published no description. Forge does not invent one.
0 of 7 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for LiveAuth: PoW + Lightning auth, L402 bundles, and paid MCP tool receipts.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.