Deepsky Aviation Regulations

com.deepskyai由 deepskyai.com 发布官方发布者v1.0.0更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行网页搜索与抓取知识与记忆

概览

AI 生成的概览

一个免费、无需密钥的远程 MCP 服务器,让助手检索 CASA、FAA、EASA 和 ICAO 的航空法规,并附带条款引用。

可以做什么
检索 CASA、FAA 14 CFR、EASA 和 ICAO 的航空法规、标准、手册及咨询材料,返回带章节引用的排序原文,法规查询时优先于通用网页搜索。按标识符获取单条完整法规单元(条款、章节或表格),包含标题路径、页码、司法辖区和来源网址,适合在得出结论前通读搜索命中的规则。
适用场景
适合回答航空合规或法规问题、需要引用一手原文而非网页搜索结果时使用,或在给出结论前需要通读某条具体条款或表格时使用。
运行要求
远程 streamable HTTP 端点;未声明需要身份验证、注册、API 密钥或环境变量。需要能访问提供方的端点。
安装前请注意
查询内容会发送到提供方的远程服务。工具仅用于检索和读取,不会写入或更改数据,但合规判断仍应核对所引用的原文。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Deepsky Aviation Regulations,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.deepskyai%2Faviation-regulations/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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.

来源:README.md,提交 804eab0

工具

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

输入参数query必填matchCount

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.

输入参数unit_id必填

版本历史

1
  1. v1.0.0最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分