Serverdex live check · status history
Lido MCP MCP server status
● Unreachablechecked Nov 22, 2026, 00:08 UTC
At the last Serverdex check (Nov 22, 2026, 00:08 UTC) the Lido MCP endpoint did not answer (err ssl ssl/tls alert handshake failure). One failed check is not a removal; it is tried again on the next pass.
Uptime, 30 days
0%
2 days on record
Uptime, 90 days
0%
2 days on record
Answering since
—
Unreachable
Tools now
—
no change on record
Status history
1 change on record · only changes are stored, not every check- First checked: unreachable
err ssl ssl/tls alert handshake failure
Questions
- Is Lido MCP down right now?
- At the last Serverdex check (Nov 22, 2026, 00:08 UTC) the Lido MCP endpoint did not answer (err ssl ssl/tls alert handshake failure). One failed check is not a removal; it is tried again on the next pass.
- How is Lido MCP checked?
- Serverdex calls the server's hosted endpoint about once a day with a plain MCP initialize followed by tools/list, with no credentials, and records only changes: a status flip or a change in the tool list. Uptime is time-weighted from those changes, so a server checked for less than a day shows no percentage.
- What does "needs sign-in" mean for Lido MCP?
- The endpoint is reachable and speaks HTTP, but returns 401 or 403 until a key or OAuth sign-in is supplied. The server is up; the Serverdex check cannot read its tools without an account.
Back to the Lido MCP listing · test any endpoint yourself with the MCP server health check · what changed across the registry today: MCP server changelog.