Remote MCP · Endpoint
me.ceki/mcp-server MCP server
No. me.ceki/mcp-server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.ceki.me/mcp/agent
The last check completed an MCP handshake.
- Registry name
- me.ceki/mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 451 ms
- Tools exposed
- 60 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Hire specialists by the hour — search, schedule, and pay via MCP protocol.
- Repository
- https://github.com/Ceki-me/mcp-server
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 451 ms |
| 1 day ago | Handshake completed | 439 ms |
| 2 days ago | Handshake completed | 439 ms |
| 3 days ago | Handshake completed | 438 ms |
| 4 days ago | Handshake completed | 434 ms |
| 5 days ago | Handshake completed | 446 ms |
| 6 days ago | Handshake completed | 452 ms |
| 8 days ago | Handshake completed | 691 ms |
| 11 days ago | Handshake completed | 429 ms |
| 13 days ago | Handshake completed | 464 ms |
| 15 days ago | Handshake completed | 446 ms |
| 18 days ago | Handshake completed | 974 ms |
| 20 days ago | Handshake completed | 430 ms |
| 22 days ago | Handshake completed | 460 ms |
| 24 days ago | Handshake completed | 430 ms |
| 26 days ago | Handshake completed | 434 ms |
| 27 days ago | Handshake completed | 454 ms |
| 28 days ago | Handshake completed | 435 ms |
| 29 days ago | Handshake completed | 1.82 s |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 me.ceki/mcp-server and makes no claim about it beyond what these checks measured.