Remote MCP · Endpoint
GeezerKeeper Referral Exit Routes and Deadlines MCP server
No. GeezerKeeper Referral Exit Routes and Deadlines answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://geezerkeeper.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.geezerkeeper/referral-exit-routes
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 158 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Read-only senior-care exit routes, duplicate-referral deadlines, and templates; no PII or sending.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 158 ms |
| 18 hours ago | Handshake completed | 126 ms |
| 2 days ago | Handshake completed | 157 ms |
| 3 days ago | Handshake completed | 138 ms |
| 4 days ago | Handshake completed | 227 ms |
| 5 days ago | Handshake completed | 227 ms |
| 6 days ago | Handshake completed | 90 ms |
| 7 days ago | Handshake completed | 186 ms |
| 10 days ago | Handshake completed | 261 ms |
| 13 days ago | Handshake completed | 411 ms |
| 15 days ago | Handshake completed | 156 ms |
| 17 days ago | Handshake completed | 170 ms |
| 19 days ago | Handshake completed | 346 ms |
| 21 days ago | Handshake completed | 270 ms |
| 23 days ago | Handshake completed | 275 ms |
| 25 days ago | Handshake completed | 276 ms |
| 27 days ago | Handshake completed | 1.36 s |
| 28 days ago | Handshake completed | 171 ms |
| 29 days ago | Handshake completed | 241 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 GeezerKeeper Referral Exit Routes and Deadlines and makes no claim about it beyond what these checks measured.