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).
Recent checks of C'est Chaud à Paris
CheckedResultHandshake
7 hours agoHandshake completed216 ms
4 days agoHandshake completed254 ms
14 days agoHandshake completed251 ms
15 days agoHandshake completed186 ms
15 days agoHandshake completed209 ms
17 days agoHandshake completed211 ms
18 days agoHandshake completed169 ms
19 days agoHandshake completed166 ms
20 days agoHandshake completed179 ms
21 days agoHandshake completed283 ms
23 days agoHandshake completed210 ms
26 days agoHandshake completed188 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.