faa-aircraft-registry-mcp-server

faa-aircraft-registry-mcp-server: get registration status

faa_get_registration_status

Read-onlyIdempotent

Resolve whether a US civil aircraft N-number is active, deregistered, reserved, or unknown, including the available registration and airworthiness status. Use this rather than faa_lookup_registration when a number may be inactive. A number that was never issued returns recordType "unknown" — a valid, informative answer, not an error. Accepts "N12345" or "12345".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`nNumber`	Yes	US registration N-number to resolve. Accepts "N12345" or "12345" (leading N optional). Shape: 1–5 characters — a leading digit 1–9, then digits, optionally ending in 1–2 letters (I and O are unused).

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`status`	No	Registration/cancellation status as code + label (active and deregistered records).
`nNumber`	No	Normalized N-number without the leading "N".
`purgeDate`	No	Scheduled purge date, YYYY-MM-DD (reserved records).
`cancelDate`	No	Cancellation date, YYYY-MM-DD (deregistered records).
`recordType`	No	Resolved registration state: active, deregistered, reserved, or unknown.
`reserveDate`	No	Date the number was reserved, YYYY-MM-DD (reserved records).
`modeSCodeHex`	No	Mode S code in hex / ICAO 24-bit address (deregistered records).
`serialNumber`	No	Manufacturer serial number (deregistered records).
`certIssueDate`	No	Certificate issue date, YYYY-MM-DD (active records).
`expirationDate`	No	Registration expiration date, YYYY-MM-DD (active records).
`nNumberDisplay`	No	N-number with the leading "N" for display.
`typeReservation`	No	Type of reservation as code + label (reserved records).
`nNumberForChange`	No	The N-number this reservation changes to/from (reserved records).
`airworthinessDate`	No	Airworthiness certificate date, YYYY-MM-DD (active records).
`airworthinessClass`	No	Airworthiness classification as code + label (active records).
`expirationNoticeDate`	No	Date an expiration notice was sent, YYYY-MM-DD (reserved records).
`manufacturerModelCode`	No	6–7-character manufacturer/model/series code (deregistered records).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedOutput schema / properties / manufacturerModelCode / description

Previous value: -"7-char manufacturer/model/series code (deregistered records)."New value: +"6–7-character manufacturer/model/series code (deregistered records)."

Changed7 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": [
+      "recordType",
+      "nNumber",
+      "nNumberDisplay"
+    ]
+  },
+  {
+    "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: `invalid_n_number`: The input is not a structurally valid N-number (after the optional leading \"N\": 1–5 characters, a leading digit 1–9, then digits, optionally 1–2 trailing letters; I and O are unused). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_n_number"
+          ],
+          "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"
+}

changedOutput schema / properties / recordType / description

Previous value: -"Which file the number resolved in: active (MASTER), deregistered (DEREG), reserved (RESERVED), or unknown (none)."New value: +"Resolved registration state: active, deregistered, reserved, or unknown."

removedOutput schema / required

Removed value: -[
-  "recordType",
-  "nNumber",
-  "nNumberDisplay"
-]

Changed1 schema field changedJul 16, 2026

changedInput schema / properties / nNumber / description

Previous value: -"US registration N-number to resolve. Accepts \"N12345\" or \"12345\"; the leading N is optional."New value: +"US registration N-number to resolve. Accepts \"N12345\" or \"12345\" (leading N optional). Shape: 1–5 characters — a leading digit 1–9, then digits, optionally ending in 1–2 letters (I and O are unused)."

First observedJun 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description nonetheless adds real semantic context beyond them: the full set of possible resolution states and the important behavioral note that an unissued number is a normal informative result, not a failure. It does not discuss rate limits or auth, but nothing suggests those are relevant here.

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?

Four short sentences, all front-loaded: purpose, sibling routing, error-semantics caveat, input format. No filler and nothing an agent would need to skip past to find the key routing instruction.

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?

An output schema exists, so return-value documentation is unnecessary, and the description supplies the one thing the schema cannot: what "unknown" means semantically and when to prefer this tool. For a single-parameter read tool, nothing material is missing.

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

Parameters3/5

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

Schema description coverage is 100% and the schema already documents the accepted "N12345"/"12345" forms and the character shape rules. The description's "Accepts 'N12345' or '12345'" merely restates that, so this is the baseline case where the schema does the heavy lifting.

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 names a specific verb (resolve) and resource (US civil aircraft N-number) and enumerates the exact outcome states it returns: active, deregistered, reserved, or unknown. It explicitly differentiates itself from the sibling faa_lookup_registration, so an agent can route without opening either schema.

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?

It states the selection condition outright: "Use this rather than faa_lookup_registration when a number may be inactive." It also pre-empts a misuse mode by clarifying that a never-issued number returns recordType "unknown" as a valid answer rather than an error.

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.