Remote MCP · Endpoint

travel.kismet/mcp-server MCP server

No. travel.kismet/mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.kismet.travel/mcp

The last check completed an MCP handshake.

Registry name
travel.kismet/mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
353 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Semantic hotel search with real-time availability and price comparison for Kismet Travel
Repository
https://github.com/kismet-tech/kismet-travel-mcp-v2
Listing
From the official MCP registry (active).
Recent checks of travel.kismet/mcp-server
CheckedResultHandshake
1 hour agoHandshake completed353 ms
2 days agoHandshake completed481 ms
4 days agoHandshake completed449 ms
6 days agoHandshake completed503 ms
7 days agoHandshake completed775 ms
8 days agoHandshake completed486 ms
9 days agoHandshake completed425 ms
12 days agoHandshake completed403 ms
13 days agoHandshake completed449 ms
15 days agoHandshake completed581 ms
17 days agoHandshake completed389 ms
18 days agoHandshake completed384 ms
19 days agoHandshake completed375 ms
20 days agoHandshake completed453 ms
21 days agoHandshake completed145 ms
21 days agoHandshake completed458 ms
23 days agoHandshake completed385 ms

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with travel.kismet/mcp-server and makes no claim about it beyond what these checks measured.