Remote MCP · Endpoint
Summer MCP server
No. Summer answered an MCP handshake 9 hours ago.
UpLast checked 9 hours ago
Server URL
https://api.gosummer.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.gosummer/summer
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 282 ms
- Tools exposed
- 235 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- Telehealth support for Claude, Codex and Cursor: investigate cases and connect your tools.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 9 hours ago | Handshake completed | 282 ms |
| 4 days ago | Handshake completed | 134 ms |
| 14 days ago | Handshake completed | 194 ms |
| 15 days ago | Handshake completed | 153 ms |
| 15 days ago | Handshake completed | 252 ms |
| 17 days ago | Handshake completed | 194 ms |
| 18 days ago | Handshake completed | 196 ms |
| 19 days ago | Handshake completed | 135 ms |
| 20 days ago | Handshake completed | 243 ms |
| 21 days ago | Handshake completed | 152 ms |
| 23 days ago | Handshake completed | 179 ms |
| 26 days ago | Handshake completed | 219 ms |
| 28 days ago | Handshake completed | 206 ms |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.
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 Summer and makes no claim about it beyond what these checks measured.