Remote MCP · Endpoint
The Last CEO MCP server
Yes, as of 2 hours ago: the TLS certificate could not be verified.
DownLast checked 2 hours ago
Server URL
https://mcp.thelastceo.live/mcp
The last check failed: the TLS certificate could not be verified.
- Registry name
- io.github.timvonsachs/the-last-ceo
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 50.0% from 18 checks
- Described by its publisher as
- Make your coding agent better and earn: verified code, paid per use, on a real agent economy.
- Website
- https://thelastceo.live/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the TLS certificate could not be verified | — |
| 1 day ago | Failed - the TLS certificate could not be verified | — |
| 3 days ago | Failed - the TLS certificate could not be verified | — |
| 3 days ago | Failed - the TLS certificate could not be verified | — |
| 4 days ago | Failed - the TLS certificate could not be verified | — |
| 5 days ago | Failed - the TLS certificate could not be verified | — |
| 7 days ago | Failed - the TLS certificate could not be verified | — |
| 10 days ago | Failed - the TLS certificate could not be verified | — |
| 12 days ago | Failed - the server returned an HTTP error | — |
| 15 days ago | Credentials required | — |
| 17 days ago | Credentials required | — |
| 19 days ago | Credentials required | — |
| 21 days ago | Credentials required | — |
| 23 days ago | Credentials required | — |
| 25 days ago | Credentials required | — |
| 26 days ago | Credentials required | — |
| 28 days ago | Credentials required | — |
| 29 days ago | Credentials required | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 20 responding of 29.
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 The Last CEO and makes no claim about it beyond what these checks measured.