Remote MCP · Endpoint
航班管家航空数据 MCP | Flight Master Aviation Data MCP MCP server
Yes, as of 1 hour ago: the server rejected the MCP handshake.
DownLast checked 1 hour ago
Server URL
https://fly.huoli.com/mcp/dast_mcp
The last check failed: the server rejected the MCP handshake.
- Registry name
- io.github.flight-master-dast/aviation-data-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- 航班管家 DAST 官方航空数据 MCP，支持 Remote HTTP 与 npm STDIO，提供航班动态、天气、轨迹及延误风险。Official Flight Master MCP.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server rejected the MCP handshake | — |
| 1 day ago | Failed - the server rejected the MCP handshake | — |
| 2 days ago | Failed - the server rejected the MCP handshake | — |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 0 responding of 3.
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 航班管家航空数据 MCP | Flight Master Aviation Data MCP and makes no claim about it beyond what these checks measured.