Remote MCP · Endpoint

MAQAMI Travel MCP server

No. MAQAMI Travel answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://mcp.maqami.co/

The last check completed an MCP handshake.

Registry name
io.github.negm17111995/maqami-travel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
440 ms
Tools exposed
35 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Official MCP server for MAQAMI, a hotel and flight booking platform with 3M+ hotels.
Listing
From the official MCP registry (active).
Recent checks of MAQAMI Travel
CheckedResultHandshake
44 minutes agoHandshake completed440 ms
3 days agoHandshake completed155 ms
13 days agoHandshake completed610 ms
13 days agoHandshake completed554 ms
15 days agoHandshake completed258 ms
15 days agoHandshake completed281 ms
17 days agoHandshake completed687 ms
18 days agoHandshake completed110 ms
18 days agoHandshake completed103 ms
20 days agoHandshake completed290 ms
22 days agoHandshake completed262 ms
25 days agoHandshake completed502 ms
27 days agoHandshake completed219 ms
29 days agoHandshake completed1.24 s

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

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