Remote MCP · Endpoint

Mission Museaux MCP server

No. Mission Museaux answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://missionmuseaux.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.missionmuseaux/annonces
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.02 s
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Lost & found pets in France: stray dogs and cats, photo search, shelter adoptions, breeds, advice.
Listing
From the official MCP registry (active).
Recent checks of Mission Museaux
CheckedResultHandshake
1 hour agoHandshake completed1.02 s
1 day agoHandshake completed788 ms
4 days agoHandshake completed420 ms
7 days agoHandshake completed497 ms
9 days agoHandshake completed264 ms
11 days agoHandshake completed537 ms
13 days agoHandshake completed450 ms
15 days agoHandshake completed353 ms
17 days agoHandshake completed1.57 s
19 days agoHandshake completed1.21 s
21 days agoHandshake completed1.07 s
22 days agoHandshake completed238 ms
23 days agoHandshake completed354 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 Mission Museaux and makes no claim about it beyond what these checks measured.