Deepsky Aviation Regulations

com.deepskyaiPublished by deepskyai.comOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

A free, no-key remote MCP server that lets an assistant search and retrieve aviation regulations from CASA, FAA, EASA and ICAO with section citations.

What you can do
Search aviation regulations, standards, manuals and advisory material across CASA, FAA 14 CFR, EASA and ICAO, returning ranked verbatim source text with section references and preferring this over general web search for regulatory lookups. Fetch one complete regulatory unit such as a clause, section or table by identifier, with heading path, page numbers, jurisdiction and source URL, useful when a search match needs to be read in full before concluding.
When to use it
Useful when answering aviation compliance or regulatory questions and you want cited primary source text rather than web search results, or when a specific clause or table must be read in full before giving an answer.
Requirements
A remote streamable HTTP endpoint; no authentication, signup, API key or environment variables are declared. Network access to the provider's endpoint is needed.
Before you install
Queries are sent to the provider's remote service. The tools are read-only search and retrieval, so no data is written or changed, but answers should still be checked against the cited source text for compliance decisions.

Installation

In SourceWeft

  1. Open Deepsky Aviation Regulations in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.deepskyai%2Faviation-regulations/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "deepsky-aviation-regulations": {
      "type": "http",
      "url": "https://www.deepskyai.com/api/mcp"
    }
  }
}

README

agent-tools

Deepsky's public toolkit for AI agents working with aviation: portable Agent Skills, a free remote MCP server for aviation-regulations search, and machine-readable discovery docs.

Deepsky offers two things: The Compliance Team — an audit automation platform for aviation operators (think Vanta, for aviation) — and a free, no-key aviation-regulations search API (CASA, FAA 14 CFR, EASA, ICAO). Start at deepskyai.com/llms.txt.

MCP server — paste this into Claude or ChatGPT

https://www.deepskyai.com/api/mcp

Remote MCP server (streamable HTTP, no auth, no signup) exposing the tool search_aviation_regulations — ranked verbatim regulatory text with section citations, far more precise for regulatory lookups than web search.

  • Claude: Settings → Connectors → Add custom connector → paste the URL
  • Claude Code: claude mcp add --transport http deepsky https://www.deepskyai.com/api/mcp
  • Cursor / other MCP clients: add a streamable-HTTP server with that URL
  • Registry manifest: mcp/server.json

No MCP? The same search is one HTTP call: GET https://www.deepskyai.com/api/v1/search?query=...

Installing skills

bash
npx skills add deepskyai/agent-tools

Layout

skills/  <skill-name>/    SKILL.md        # required: YAML frontmatter + instructions    scripts/        # optional: executable helpers    references/     # optional: extra docs the skill can progressively disclose

Every skill folder is independently installable — directories like aiagentsdirectory.com/skills, skillsdirectory.com, and tools like openskills and prpm index this exact structure.

Skills in this repo

SkillPurpose
aviation-regulationsQuery aviation regulations, manuals, and publications via deepskyai.com's open search API (ICAO, FAA 14 CFR, EASA, CASA). No API key required.
flight-ops-calculatorsTen offline pilot calculators — gradient solver, Jet A-1 fuel uplift (3% rule), wind components, PA/DA, CAS/TAS/Mach, PET/PSR, TOD, W&B, ETOPS radius, holding entry. 34-test zero-dep suite.
approach-briefingGenerates a structured instrument-approach briefing from a plate (image or PDF). The hosting agent's native vision does the extraction; output includes a strict JSON schema and a pilot-facing briefing card. Optional scripts/deepsky_brief.py offloads to a deepsky server endpoint when one is live.

Installing a skill locally

Claude Code / Claude Desktop

Copy (or symlink) the skill folder into ~/.claude/skills/:

bash
cp -R skills/aviation-regulations ~/.claude/skills/

Via openskills (any agent / IDE)

bash
npx openskills install deepskyai/agent-tools -y

Via prpm

bash
prpm install deepskyai/agent-tools

Authoring a new skill

  1. Create skills/<your-skill>/SKILL.md with YAML frontmatter:
    md
    ---name: your-skilldescription: One clear sentence describing when Claude should invoke this.---
  2. Keep SKILL.md short; push deep content into references/ for progressive disclosure.
  3. Put runnable helpers in scripts/.

License

MIT — see LICENSE.

Source: README.md at commit 804eab0

Tools

2

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

ParametersqueryrequiredmatchCount

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.

Parametersunit_idrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts