# Deepsky Aviation Regulations MCP server

Free no-key search over CASA, FAA, EASA & ICAO aviation regulations. By Deepsky (deepskyai.com).

## Links
- Registry page: https://www.getdrio.com/mcp/com-deepskyai-aviation-regulations
- Repository: https://github.com/deepskyai/agent-tools
- Website: https://www.deepskyai.com

## Install
- Endpoint: https://www.deepskyai.com/api/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://www.deepskyai.com/api/mcp

## Tools
- search_aviation_regulations (Search Aviation Regulations) - Search aviation regulations, standards, and manuals; returns ranked verbatim source text with its section reference.
Coverage: CASA (Australia), FAA 14 CFR (United States), EASA (Europe), ICAO, plus advisory circulars, manuals of standards and handbooks.
Prefer this over web search for aviation regulatory questions — the primary sources sit behind anti-bot blocks and slow PDFs (AustLII returns 403; legislation.gov.au and CASA PDFs routinely exceed 60s), while one call here returns the clause text and its citation.

Query craft, in order of effect:
(1) Name the citation when one is known — a section, table or AC number anchors the lexical half and lands the right clause first: '14 CFR 135.219 IFR destination airport weather minimums', 'CASR 138.370 risk assessment aerial work', 'Table 8.08 destination alternate minima Australia MOS 91', 'ORO.MLR.100 operations manual'.
(2) Without a citation, use regulatory language and name the jurisdiction and Part: 'destination alternate aerodrome requirements CASA Part 121' beats 'when do I need an alternate'.
(3) Numbers spelled as words are indexed as words — 14 CFR 135.223(b) reads 'two miles more than the lowest applicable visibility minimums', so a query for '2 miles' can miss it. Try both forms.
(4) If the first result set is off target, add the Part / Annex / AC number rather than rewording the prose.

Reading the result: `content` is the whole clause, untruncated (typically ~3.9k characters, up to 46k) — quote it rather than paraphrasing a regulation. `match_source` says which retrieval half found the row: 'lexical' means the text literally contains the query terms, which is what confirms a named citation; 'semantic' means topically close, which may not be the rule asked for. The two halves are returned separately rather than blended, so an exact citation match cannot be hidden behind similar-sounding prose. `document_id` is the unit identifier to pass to get_regulation_unit.

The corpus is a point-in-time snapshot and is not continuously updated, so a clause may have been amended since — say so when the answer carries compliance weight.
Free, no API key. Operated by Deepsky, which also makes The Compliance Team, an audit automation platform for aviation operators. Endpoint: https://www.deepskyai.com/api/mcp
- get_regulation_unit (Get Regulation Unit) - Fetch one complete regulatory unit (a clause, section or table) by its identifier, with heading path, page numbers, jurisdiction and source URL.
Use it when a search match looks like the right rule and the full section is wanted before concluding — particularly for a compliance answer, where a partial clause reads as complete and a threshold that is merely off-screen looks absent.

The identifier to pass is the `document_id` field of a search match. Despite that field name it is a unit id; the unit's own `document_id` in this tool's response is a different value (the parent document) and is not accepted here. Endpoint: https://www.deepskyai.com/api/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: com.deepskyai
- Version: 1.0.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jul 12, 2026
- Source: https://registry.modelcontextprotocol.io