Remote MCP · Endpoint
AirCargoMCP MCP server
No. AirCargoMCP answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://mcp.aircargomcp.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.navo24/air-cargo-tracking
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 188 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 11 checks
- Described by its publisher as
- Air waybill (AWB) tracking across 80 cargo airlines, normalised to IATA Cargo-IMP milestones.
- Website
- https://aircargomcp.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 188 ms |
| 4 days ago | Handshake completed | 131 ms |
| 14 days ago | Handshake completed | 119 ms |
| 15 days ago | Handshake completed | 192 ms |
| 15 days ago | Handshake completed | 113 ms |
| 17 days ago | Handshake completed | 148 ms |
| 18 days ago | Handshake completed | 111 ms |
| 19 days ago | Handshake completed | 114 ms |
| 20 days ago | Handshake completed | 114 ms |
| 21 days ago | Handshake completed | 185 ms |
| 23 days ago | Handshake completed | 113 ms |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.
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 AirCargoMCP and makes no claim about it beyond what these checks measured.