faa-aircraft-registry-mcp-server

faa-aircraft-registry-mcp-server: search registrations

faa_search_registrations

Read-onlyIdempotent

Search active US civil aircraft registrations by owner name, make/model, state, aircraft type, or Mode S (hex) code. Returns decoded summaries with N-numbers to drill into via faa_lookup_registration. At least one filter is required. Owner-name search is unavailable when this deployment redacts owner PII — search by make/model, state, aircraft type, or Mode S code instead. Every response reports totalCount (all matches, not just this page); when more remain, it returns nextOffset — pass it back as offset to page forward.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return (1–200, default 25).
`state`	No	Two-letter state/territory abbreviation (exact match).
`offset`	No	Zero-based index of the first result to return — pass the nextOffset from a previous response, with identical filters, to page forward (default 0).
`makeModel`	No	Aircraft make and/or model to match (full-text).
`modeSCode`	No	Mode S code in hex to match exactly (ICAO 24-bit address).
`ownerName`	No	Registrant name to match (full-text). Rejected when owner-PII redaction is on.
`aircraftType`	No	Aircraft type code to match exactly (e.g. "4" for fixed-wing single-engine).

Output Schema

TableJSON Schema

Name	Required	Description
`cap`	No	The limit that was applied (present only when truncated is set).
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of results on this page (present only when truncated is set).
`notice`	No	Guidance when no registrations matched, or when more matches remain.
`truncated`	No	Present and true only when matches remain beyond this page.
`nextOffset`	No	Offset to request the next page; absent when this page reached the end of the matches.
`totalCount`	No	Total registrations matching the filters, across all pages. Always present.
`registrations`	No	Matching registration summaries for this page (up to limit).

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "registrations",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `owner_search_disabled`: ownerName was supplied while owner-PII redaction is enabled on this deployment. `no_filters`: No search filter was supplied. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "owner_search_disabled",
+            "no_filters"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "registrations",
-  "totalCount"
-]

Changed9 schema fields changedJul 16, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Zero-based index of the first result to return — pass the nextOffset from a previous response, with identical filters, to page forward (default 0).",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

changedOutput schema / properties / cap / description

Previous value: -"The limit that was applied (present only when capped)."New value: +"The limit that was applied (present only when truncated is set)."

addedOutput schema / properties / nextOffset

Added value: +{
+  "description": "Offset to request the next page; absent when this page reached the end of the matches.",
+  "type": "number"
+}

changedOutput schema / properties / notice / description

Previous value: -"Guidance when no registrations matched the supplied filters."New value: +"Guidance when no registrations matched, or when more matches remain."

changedOutput schema / properties / registrations / description

Previous value: -"Matching registration summaries (up to limit)."New value: +"Matching registration summaries for this page (up to limit)."

changedOutput schema / properties / shown / description

Previous value: -"Number of results returned (present only when capped)."New value: +"Number of results on this page (present only when truncated is set)."

addedOutput schema / properties / totalCount

Added value: +{
+  "description": "Total registrations matching the filters, across all pages. Always present.",
+  "type": "number"
+}

changedOutput schema / properties / truncated / description

Previous value: -"Present and true only when the result set was capped at the limit — more matches exist."New value: +"Present and true only when matches remain beyond this page."

changedOutput schema / required

Previous value: -[
-  "registrations"
-]New value: +[
+  "registrations",
+  "totalCount"
+]

First observedJun 16, 2026

TDQS

A5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds crucial behavioral details beyond those: the requirement for at least one filter, the owner-PII redaction condition, and the pagination mechanism (totalCount, nextOffset, offset). These are non-obvious behaviors that would otherwise be unknown. No contradiction with annotations exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences with zero filler. It leads with the core purpose, then covers the required-filter constraint and the redaction caveat, and finishes with pagination behavior. Every sentence contributes essential information, and the structure is logical — purpose first, then constraints, then continuation mechanics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 7 optional parameters, an output schema, and a pagination design, the description covers all critical operational aspects: search fields, output format, mandatory-filter condition, deployment-specific redaction, and pagination flow. It even names the follow-up tool (faa_lookup_registration). There is no missing information an agent would need to invoke it correctly, especially given the annotations already cover read-only idempotency.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with individual parameter descriptions, providing a baseline of 3. The description adds meaningful context on top: it clarifies that at least one filter is required (a cross-parameter constraint not in the JSON Schema, since no property is marked required), and it explains how offset relates to pagination via nextOffset. It also reinforces the ownerName rejection condition, tying the parameter to the deployment context. This goes beyond mere parameter listing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Search active US civil aircraft registrations' and lists the searchable fields. It clearly distinguishes itself from the sibling tools by mentioning the drill-in step to faa_lookup_registration, establishing it as the search entry point rather than a lookup. The output expectation ('decoded summaries with N-numbers') is also stated, leaving no ambiguity about the tool's role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states a hard requirement ('At least one filter is required') and provides conditional guidance for when owner-name search is unavailable ('search by make/model, state, aircraft type, or Mode S code instead'). It also gives precise pagination instructions, telling the agent to pass nextOffset back as offset. This is actionable, context-specific guidance that distinguishes when and how to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All faa-aircraft-registry-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.