Remote MCP · Endpoint

Paris Events MCP server

No. Paris Events answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/paris-events/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/paris-events
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
51 ms
Tools exposed
37 tools
Uptime, last 30 days
87.5% from 16 checks
Described by its publisher as
Que Faire à Paris MCP.
Listing
From the official MCP registry (active).
Recent checks of Paris Events
CheckedResultHandshake
1 day agoHandshake completed51 ms
3 days agoFailed - the request timed out—
5 days agoFailed - the request timed out—
7 days agoHandshake completed65 ms
8 days agoHandshake completed55 ms
9 days agoHandshake completed116 ms
12 days agoHandshake completed46 ms
13 days agoHandshake completed48 ms
15 days agoHandshake completed77 ms
16 days agoHandshake completed45 ms
18 days agoHandshake completed45 ms
19 days agoHandshake completed43 ms
20 days agoHandshake completed48 ms
20 days agoHandshake completed52 ms
21 days agoHandshake completed57 ms
23 days agoHandshake completed59 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 16.

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 Paris Events and makes no claim about it beyond what these checks measured.