Remote MCP · Endpoint

Kompare travel search MCP server

No. Kompare travel search answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://mcp.kompare.io/mcp

The last check completed an MCP handshake.

Registry name
io.kompare/search
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
508 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Live prices on package holidays and niche trips from Danish travel agencies, with booking links.
Listing
From the official MCP registry (active).
Recent checks of Kompare travel search
CheckedResultHandshake
20 minutes agoHandshake completed508 ms
9 days agoHandshake completed502 ms
9 days agoHandshake completed519 ms
11 days agoHandshake completed495 ms
12 days agoHandshake completed696 ms
13 days agoHandshake completed491 ms
14 days agoHandshake completed505 ms
15 days agoHandshake completed526 ms
16 days agoHandshake completed507 ms
19 days agoHandshake completed564 ms
21 days agoHandshake completed578 ms
24 days agoHandshake completed490 ms
26 days agoHandshake completed514 ms
28 days agoHandshake completed501 ms

The last 14 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 Kompare travel search and makes no claim about it beyond what these checks measured.