FlightFinder Aviation Safety Data
REMOTE · HIMAXYM.COM · SCANNED SEP 21
Aviation accident narratives from 128 official authorities, plus FAA wildlife, laser and drone data
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 754 tokens (~83/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the FlightFinder Aviation Safety Data MCP server?
FlightFinder Aviation Safety Data is a hosted endpoint at https://himaxym.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · himaxym.com
claude mcp add --transport http com-himaxym-flightfinder-aviation-safety 'https://himaxym.com/mcp'
{
"mcpServers": {
"com-himaxym-flightfinder-aviation-safety": {
"url": "https://himaxym.com/mcp"
}
}
} {
"servers": {
"com-himaxym-flightfinder-aviation-safety": {
"type": "http",
"url": "https://himaxym.com/mcp"
}
}
} [mcp_servers.com-himaxym-flightfinder-aviation-safety] url = "https://himaxym.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-himaxym-flightfinder-aviation-safety": {
"type": "remote",
"url": "https://himaxym.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-himaxym-flightfinder-aviation-safety --url 'https://himaxym.com/mcp' --transport streamable-http
mcp_servers:
com-himaxym-flightfinder-aviation-safety:
url: "https://himaxym.com/mcp" {
"McpServers": {
"com-himaxym-flightfinder-aviation-safety": {
"Transport": "http",
"Url": "https://himaxym.com/mcp"
}
}
} assistant mcp add com-himaxym-flightfinder-aviation-safety -t streamable-http -u 'https://himaxym.com/mcp'
{
"mcpServers": {
"com-himaxym-flightfinder-aviation-safety": {
"type": "http",
"url": "https://himaxym.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://himaxym.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=himaxym.com | CN=WE1,O=Google Trust Services,C=US | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 6855afc6991c6cf70e0bc54538847b2a |
| SANs: himaxym.com, *.himaxym.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of himaxym.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| himaxym.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' data:;form-action 'self';frame-ancestors 'none';img-src 'self' data: https:;object-src 'none';script-src 'self' https://www.googletagmanager.com https://static.cloudflareinsights.com https://googleads.g.doubleclick.net https://www.googleadservices.com https://pagead2.googlesyndication.com https://connect.facebook.net https://*.clarity.ms https://c.bing.com;script-src-attr 'none';style-src 'self' 'unsafe-inline';upgrade-insecure-requests;connect-src 'self' https://www.google-analytics.com https://region1.google-analytics.com https://analytics.google.com https://cloudflareinsights.com https://www.google.com https://ad.doubleclick.net https://googleads.g.doubleclick.net https://www.googleadservices.com https://pagead2.googlesyndication.com https://www.facebook.com https://connect.facebook.net https://*.clarity.ms https://c.bing.com;frame-src 'self' https://www.googletagmanager.com https://td.doubleclick.net |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | geolocation=(self), camera=(), microphone=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://himaxym.com/mcp | Verified | 200 | |
| http (plaintext) | http://himaxym.com/mcp | HTTPS enforced | 301 | https://himaxym.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
aircraft_safety ~52
Aggregate safety statistics for an aircraft family: total occurrences, hull losses, fatal accidents, total fatalities, and first/latest year.
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | yes | family slug, e.g. "airbus-a320" |
| Name | Type | Req | Description |
|---|---|---|---|
| family | object | – | the family this covers |
| stats | object | – | aggregates over the merged corpus |
| types | array | – | ICAO type designators in the family |
No examples provided.
airport_reference ~51
Resolve an airport by ICAO ident or IATA code (OurAirports, CC0). Returns name, city, country, and coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| ident | string | yes | ICAO ident or IATA code |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
drone_sightings ~77
FAA UAS (drone) Sighting Reports filed by pilots and controllers (US-government public domain). With no arguments: national totals, the yearly series and the leading states and cities. Pass state for that breakdown, as a lowercase hyphenated slug.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | US state slug for a per-state breakdown. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | global totals, or the breakdown for one state |
No examples provided.
get_accident ~43
Fetch one occurrence by its FlightFinder id, with source-attribution links and references to the narratives available for it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | FlightFinder occurrence id |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
get_narrative ~97
Fetch an investigation narrative by (source, case id). Open-licensed sources return full text; others return a ≤300-char excerpt plus a source_url deep link (per-source licensing policy). id URL-encoding is handled for you — pass the raw case id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | the source’s own case id |
| source | string | yes | source code, e.g. "ntsb" (see list_sources) |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
laser_incidents ~85
FAA Reported Laser Incidents — lasers aimed at aircraft (US-government public domain). With no arguments: national totals, injuries and the yearly series. Pass state OR airport for that breakdown, as a lowercase hyphenated slug.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | – | Airport slug for a per-airport breakdown. |
| state | string | – | US state slug for a per-state breakdown. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | global totals, or the breakdown for one state or airport |
No examples provided.
list_sources ~33
List every data source in the corpus with its license, homepage, narrative count, and republication policy (full vs excerpt).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | every source in the corpus |
No examples provided.
search_accidents ~210
Search the merged aviation-accident corpus (80+ official agencies, occurrence-level dedup). Filters: aircraft family slug (e.g. "boeing-737"), ISO alpha-2 country, occurrence type, operator substring, date range (from/to as YYYY-MM-DD), and fatal-only. Returns a page of occurrences with source-attribution links and a next_cursor for pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166 alpha-2 code, e.g. "US" |
| cursor | string | – | next_cursor from a previous call |
| family | string | – | aircraft family slug, e.g. "boeing-737" |
| fatal | boolean | – | only fatal occurrences |
| from | string | – | earliest date, YYYY-MM-DD |
| limit | integer | – | occurrences per page, 1-100 |
| operator | string | – | operator name substring |
| to | string | – | latest date, YYYY-MM-DD |
| type | string | – | occurrence type code |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | one page of occurrences |
| next_cursor | string | – | pass back as cursor for the next page; absent on the last page |
No examples provided.
wildlife_strikes ~106
FAA National Wildlife Strike Database (US-government public domain). With no arguments: global totals, the full yearly series since 1990, and the leading airports, species and flight phases. Pass airport OR species for that breakdown. Slugs are lowercase and hyphenated (e.g. "kden", "mourning-dove").
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | – | Airport slug for a per-airport breakdown. |
| species | string | – | Species slug for a per-species breakdown. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | global totals, or the breakdown for one airport or species |
No examples provided.
What is the FlightFinder Aviation Safety Data MCP server?
FlightFinder Aviation Safety Data is an MCP server listed in the public MCP registry as com.himaxym/flightfinder-aviation-safety. Aviation accident narratives from 128 official authorities, plus FAA wildlife, laser and drone data. This page covers its hosted endpoint (https://himaxym.com/mcp).
Is the FlightFinder Aviation Safety Data MCP server safe to use?
FlightFinder Aviation Safety Data scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FlightFinder Aviation Safety Data MCP server expose?
FlightFinder Aviation Safety Data exposes 9 tools: search_accidents, get_accident, get_narrative, aircraft_safety, list_sources, and 4 more. Their descriptions and schemas cost roughly 754 tokens of context every time the server is loaded.
Does the FlightFinder Aviation Safety Data MCP server require authentication?
No. We connected to FlightFinder Aviation Safety Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FlightFinder Aviation Safety Data MCP server still maintained?
FlightFinder Aviation Safety Data is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.