Remote MCP · Endpoint
Deepsky Aviation Regulations MCP server
No. Deepsky Aviation Regulations answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://www.deepskyai.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.deepskyai/aviation-regulations
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 303 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 84.2% from 19 checks
- Described by its publisher as
- Free no-key search over CASA, FAA, EASA & ICAO aviation regulations. By Deepsky (deepskyai.com).
- Website
- https://www.deepskyai.com/
- Repository
- https://github.com/deepskyai/agent-tools
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 303 ms |
| 18 hours ago | Handshake completed | 343 ms |
| 2 days ago | Handshake completed | 752 ms |
| 3 days ago | Handshake completed | 302 ms |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 6 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Handshake completed | 314 ms |
| 10 days ago | Handshake completed | 281 ms |
| 13 days ago | Handshake completed | 1.02 s |
| 15 days ago | Handshake completed | 319 ms |
| 17 days ago | Handshake completed | 388 ms |
| 19 days ago | Handshake completed | 279 ms |
| 21 days ago | Handshake completed | 282 ms |
| 23 days ago | Handshake completed | 793 ms |
| 25 days ago | Handshake completed | 300 ms |
| 27 days ago | Handshake completed | 295 ms |
| 28 days ago | Handshake completed | 320 ms |
| 29 days ago | Handshake completed | 855 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 30.
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 Deepsky Aviation Regulations and makes no claim about it beyond what these checks measured.