Remote MCP · Endpoint
LION — Verified Company & Compliance Data MCP server
No. LION — Verified Company & Compliance Data answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://lionx402.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.lionx402/lion-x402
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 536 ms
- Tools exposed
- 37 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Keyless x402 compliance on Base: $0.001 OFAC wallet screen, $0.05 pack, $0.95 company file.
- Website
- https://lionx402.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 536 ms |
| 19 hours ago | Handshake completed | 932 ms |
| 2 days ago | Handshake completed | 188 ms |
| 3 days ago | Handshake completed | 269 ms |
| 4 days ago | Handshake completed | 329 ms |
| 5 days ago | Handshake completed | 304 ms |
| 6 days ago | Handshake completed | 462 ms |
| 7 days ago | Handshake completed | 306 ms |
| 10 days ago | Handshake completed | 261 ms |
| 13 days ago | Handshake completed | 673 ms |
| 15 days ago | Handshake completed | 625 ms |
| 17 days ago | Handshake completed | 303 ms |
| 19 days ago | Handshake completed | 389 ms |
| 21 days ago | Handshake completed | 430 ms |
| 23 days ago | Handshake completed | 185 ms |
| 25 days ago | Handshake completed | 240 ms |
| 27 days ago | Handshake completed | 241 ms |
| 28 days ago | Handshake completed | 291 ms |
| 29 days ago | Handshake completed | 422 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 LION — Verified Company & Compliance Data and makes no claim about it beyond what these checks measured.