Remote MCP · Endpoint

Myrmigo MCP server

No. Myrmigo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.myrmigo.com/mcp

The last check completed an MCP handshake.

Registry name
com.myrmigo/myrmigo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
129 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Travel booking reference: official sites, who services a booking, EU261/UK261 compensation checks
Listing
From the official MCP registry (active).
Recent checks of Myrmigo
CheckedResultHandshake
1 hour agoHandshake completed129 ms
2 days agoHandshake completed119 ms
4 days agoHandshake completed140 ms
6 days agoHandshake completed213 ms
7 days agoHandshake completed126 ms
9 days agoHandshake completed229 ms
10 days agoHandshake completed224 ms
11 days agoHandshake completed125 ms
14 days agoHandshake completed129 ms
15 days agoHandshake completed257 ms
17 days agoHandshake completed214 ms
18 days agoHandshake completed220 ms
19 days agoHandshake completed306 ms
20 days agoHandshake completed224 ms
21 days agoHandshake completed117 ms
21 days agoHandshake completed241 ms

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

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