Remote MCP · Endpoint

Compera MCP server

No. Compera answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://compera.se/mcp

The last check completed an MCP handshake.

Registry name
io.github.fredxhansson-cmyk/compera
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
132 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Live Swedish price & service comparison (products, broadband, mobile, electricity, loans)
Listing
From the official MCP registry (active).
Recent checks of Compera
CheckedResultHandshake
2 hours agoHandshake completed132 ms
2 days agoHandshake completed745 ms
4 days agoHandshake completed121 ms
5 days agoHandshake completed111 ms
7 days agoHandshake completed328 ms
8 days agoHandshake completed101 ms
9 days agoHandshake completed134 ms
12 days agoHandshake completed100 ms
13 days agoHandshake completed143 ms
15 days agoHandshake completed93 ms
17 days agoHandshake completed109 ms
18 days agoHandshake completed110 ms
19 days agoHandshake completed99 ms
20 days agoHandshake completed102 ms
20 days agoHandshake completed96 ms
21 days agoCredentials required—
22 days agoCredentials required—

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

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