Remote MCP · Endpoint

WeekSpots MCP server

No. WeekSpots answered an MCP handshake 45 minutes ago.

UpLast checked 45 minutes ago

Server URL

https://app.weekspots.com/mcp

The last check completed an MCP handshake.

Registry name
com.weekspots/events
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
150 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Upcoming events and outings in Paris and Île-de-France, plus permanent places across France.
Listing
From the official MCP registry (active).
Recent checks of WeekSpots
CheckedResultHandshake
45 minutes agoHandshake completed150 ms
3 days agoHandshake completed101 ms
12 days agoHandshake completed89 ms
13 days agoHandshake completed55 ms
14 days agoHandshake completed71 ms
15 days agoHandshake completed182 ms
16 days agoHandshake completed83 ms
17 days agoHandshake completed92 ms
18 days agoHandshake completed56 ms
19 days agoHandshake completed74 ms
22 days agoHandshake completed133 ms
25 days agoHandshake completed140 ms
27 days agoHandshake completed988 ms

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

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

WeekSpots MCP server - status, uptime and latency - Glide