Remote MCP · Endpoint
Lightning Wallet MCP server
No. Lightning Wallet answered an MCP handshake 56 minutes ago.
UpLast checked 56 minutes ago
Server URL
https://lightningfaucet.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.lightningfaucet/lightning-wallet-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 290 ms
- Tools exposed
- 86 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 56 minutes ago | Handshake completed | 290 ms |
| 3 days ago | Handshake completed | 219 ms |
| 12 days ago | Handshake completed | 240 ms |
| 13 days ago | Handshake completed | 329 ms |
| 15 days ago | Handshake completed | 446 ms |
| 15 days ago | Handshake completed | 190 ms |
| 17 days ago | Handshake completed | 223 ms |
| 18 days ago | Handshake completed | 242 ms |
| 18 days ago | Handshake completed | 385 ms |
| 20 days ago | Handshake completed | 294 ms |
| 22 days ago | Handshake completed | 296 ms |
| 25 days ago | Credentials required | — |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Lightning Wallet and makes no claim about it beyond what these checks measured.