Remote MCP · Endpoint
C'est Chaud à Paris MCP server
No. C'est Chaud à Paris answered an MCP handshake 7 hours ago.
UpLast checked 7 hours ago
Server URL
https://cestchaud.city/mcp
The last check completed an MCP handshake.
- Registry name
- city.cestchaud/paris
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 216 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Read-only Paris catalogue: events and dates, places, free things, booking links.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 7 hours ago | Handshake completed | 216 ms |
| 4 days ago | Handshake completed | 254 ms |
| 14 days ago | Handshake completed | 251 ms |
| 15 days ago | Handshake completed | 186 ms |
| 15 days ago | Handshake completed | 209 ms |
| 17 days ago | Handshake completed | 211 ms |
| 18 days ago | Handshake completed | 169 ms |
| 19 days ago | Handshake completed | 166 ms |
| 20 days ago | Handshake completed | 179 ms |
| 21 days ago | Handshake completed | 283 ms |
| 23 days ago | Handshake completed | 210 ms |
| 26 days ago | Handshake completed | 188 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 C'est Chaud à Paris and makes no claim about it beyond what these checks measured.