mcp-registry/com.deepskyai/aviation-regulations · v1.1.0
As of 2026-10-26 09:10 UTC, the Deepskyai Aviation Regulations MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 3 minutes.
Free no-key search over CASA, FAA, EASA & ICAO aviation regulations. By Deepsky (deepskyai.com).
Claude Code
claude mcp add --transport http deepskyai-aviation-regulations-mcp-serve https://www.deepskyai.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"deepskyai-aviation-regulations-mcp-serve": {
"type": "http",
"url": "https://www.deepskyai.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.deepskyai%2Faviation-regulations/fixes
{
"name": "get_regulation_unit",
"description": "Fetch one complete regulatory unit (a clause, section or table) by its identifier, with heading path, page numbers, jurisdiction and source URL.\nUse 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.\n\nThe identifier to pass is the `document_id` field of a search match. Despite that field name it is a unit id; the u",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"unit_id"
],
"properties": {
"unit_id": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The `document_id` value from a search match — a UUID identifying one regulatory unit."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get Regulation Unit"
}{
"name": "search_aviation_regulations",
"description": "Search aviation regulations, standards, and manuals; returns ranked verbatim source text with its section reference.\nCoverage: CASA (Australia), FAA 14 CFR (United States), EASA (Europe), ICAO, plus advisory circulars, manuals of standards and handbooks.\nPrefer 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 tex",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"maxLength": 2000,
"minLength": 1,
"description": "Natural-language question or keywords. Include the citation if one is known — e.g. 'CASR 138.370 risk assessment aerial work' or '14 CFR 135.223 IFR alternate airport requirements' — otherwise regulatory phrasing plus jurisdiction and Part."
},
"matchCount": {
"type": "integer",
"default": 8,
"maximum": 20,
"minimum": 1,
"description": "Number of ranked matches to return (1-20)."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Search Aviation Regulations"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.deepskyai/aviation-regulations"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.deepskyai/aviation-regulations"}) over MCP.
search_aviation_regulations ~311 tokensget_regulation_unit ~232 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.deepskyai%2Faviation-regulations?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.deepskyai%2Faviation-regulations?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.deepskyai%2Faviation-regulations.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.deepskyai%2Faviation-regulations.svg :target: https://glimind.com/server/mcp-registry%2Fcom.deepskyai%2Faviation-regulations?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3353ae9e1de34e10…, first seen 2026-10-17, included at leaf 583 of 71,862. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 09:10 UTC, the Deepskyai Aviation Regulations MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 3 minutes.
Deepskyai Aviation Regulations MCP server advertises 2 tools, including get_regulation_unit, search_aviation_regulations.
Point your MCP client at this streamable-http endpoint: https://www.deepskyai.com/api/mcp
Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.