Remote MCP · Endpoint

Comparr MCP server

No. Comparr answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://www.comparr.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.comparr/comparr
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
187 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Compare prices across French merchants, with recorded price history and verified price drops.
Listing
From the official MCP registry (active).
Recent checks of Comparr
CheckedResultHandshake
2 hours agoHandshake completed187 ms
2 days agoHandshake completed169 ms
4 days agoHandshake completed552 ms
6 days agoHandshake completed190 ms
8 days agoHandshake completed362 ms
10 days agoHandshake completed174 ms
11 days agoHandshake completed209 ms
13 days agoHandshake completed153 ms
14 days agoHandshake completed173 ms
15 days agoHandshake completed167 ms
18 days agoHandshake completed191 ms
19 days agoHandshake completed167 ms
21 days agoHandshake completed181 ms
23 days agoHandshake completed167 ms
24 days agoHandshake completed204 ms

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

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