protogrid

Search / com.deepskyai/aviation-regulations

Deepsky Aviation Regulations

R0· no sign-in

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

v1.0.0 · active · repository · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality76good
Trust93of 100
Uptime, 30 days100%
Latency p50529 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "aviation-regulations": {
      "type": "http",
      "url": "https://www.deepskyai.com/api/mcp"
    }
  }
}
claude mcp add --transport http aviation-regulations https://www.deepskyai.com/api/mcp
[mcp_servers.aviation-regulations]
url = "https://www.deepskyai.com/api/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aviation-regulations": {
      "type": "remote",
      "url": "https://www.deepskyai.com/api/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "aviation-regulations": {
      "type": "http",
      "url": "https://www.deepskyai.com/api/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=aviation-regulations&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vd3d3LmRlZXBza3lhaS5jb20vYXBpL21jcCJ9"
}
{
  "servers": {
    "aviation-regulations": {
      "type": "http",
      "url": "https://www.deepskyai.com/api/mcp"
    }
  }
}
{
  "mcpServers": {
    "aviation-regulations": {
      "httpUrl": "https://www.deepskyai.com/api/mcp"
    }
  }
}
extensions:
  "aviation-regulations":
    enabled: true
    name: "aviation-regulations"
    type: streamable_http
    uri: "https://www.deepskyai.com/api/mcp"
    timeout: 300

Quality 76 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene64 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • warn
    tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_regulation_unit (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_aviation_regulations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
  • pass
    tools.token_costabout 933 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

2 tools, about 933 tokens to load them all · tool set b356c3ad1942 · checked 2026-10-20 15:57 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 93 / 100

provenance100
liveness100
freshness65
hygiene100

+repository +namespace-matches-repo +dns-namespace +website +reachable +uptime-100% ~updated-100d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://www.deepskyai.com/api/mcp streamable-httpnoneyes100%529 ms2025-11-252026-10-20

Tools (2)

get_regulation_unitFetch 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.
search_aviation_regulationsSearch 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.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "com.deepskyai/aviation-regulations",
  "title": "Deepsky Aviation Regulations",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://www.deepskyai.com/api/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "repository": {
    "url": "https://github.com/deepskyai/agent-tools",
    "source": "github"
  },
  "websiteUrl": "https://www.deepskyai.com",
  "description": "Free no-key search over CASA, FAA, EASA & ICAO aviation regulations. By Deepsky (deepskyai.com)."
}