Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FlightFinder Aviation Safety Data

REMOTE · HIMAXYM.COM

Aviation accident narratives from 128 official authorities, plus FAA wildlife, laser and drone data

Available components

0 this week 87 Trust /100

Last scanned (10 hours ago)

Scores higher than 94% of remote servers

Reachable. Last reached 7 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 7 Nov 26 0
    • Endpoint reachability: not serving MCP → reachable ▲ functional
  • 6 Nov 26 +64
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 −64
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 30 Sept 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Sept 26 0
    • Authorization: unverified → partial ▲ security
    • Schema quality: 478 → 754 ▼ functional
    • Tool coverage: 93% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Tool “aircraft_safety” now declares an output schema ▲ functional
    • Tool “airport_reference” now declares an output schema ▲ functional
    • Tool “get_accident” now declares an output schema ▲ functional
    • Tool “get_narrative” now declares an output schema ▲ functional
    • Tool “list_sources” now declares an output schema ▲ functional
    • Tool “search_accidents” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • New tool “drone_sightings” functional
    • New tool “laser_incidents” functional
    • New tool “wildlife_strikes” functional
    • “search_accidents” reworded the description of “limit” cosmetic
  • 31 Aug 26 0

    First indexed and scored.

Diagnostics

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 7 Nov 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 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 30fe9a7c68f4581d0e57c0508771c09b
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. DS published 19718 13 Verified
himaxym.com. No DS 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://*.google-analytics.com https://analytics.google.com https://*.analytics.google.com https://cloudflareinsights.com https://www.google.com https://ad.doubleclick.net https://*.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
MCP tools · 9 exposed · ~754 tokens

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 →

Tool Tokens
aircraft_safety ~52

Aggregate safety statistics for an aircraft family: total occurrences, hull losses, fatal accidents, total fatalities, and first/latest year.

NameTypeReqDescription
familystringyesfamily slug, e.g. "airbus-a320"
NameTypeReqDescription
familyobject–the family this covers
statsobject–aggregates over the merged corpus
typesarray–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.

NameTypeReqDescription
identstringyesICAO ident or IATA code
NameTypeReqDescription
dataobjectyes–

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.

NameTypeReqDescription
statestring–US state slug for a per-state breakdown.
NameTypeReqDescription
dataobjectyesglobal 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.

NameTypeReqDescription
idstringyesFlightFinder occurrence id
NameTypeReqDescription
dataobjectyes–

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.

NameTypeReqDescription
idstringyesthe source’s own case id
sourcestringyessource code, e.g. "ntsb" (see list_sources)
NameTypeReqDescription
dataobjectyes–

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.

NameTypeReqDescription
airportstring–Airport slug for a per-airport breakdown.
statestring–US state slug for a per-state breakdown.
NameTypeReqDescription
dataobjectyesglobal 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.

NameTypeReqDescription
dataarrayyesevery 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.

NameTypeReqDescription
countrystring–ISO 3166 alpha-2 code, e.g. "US"
cursorstring–next_cursor from a previous call
familystring–aircraft family slug, e.g. "boeing-737"
fatalboolean–only fatal occurrences
fromstring–earliest date, YYYY-MM-DD
limitinteger–occurrences per page, 1-100
operatorstring–operator name substring
tostring–latest date, YYYY-MM-DD
typestring–occurrence type code
NameTypeReqDescription
dataarrayyesone page of occurrences
next_cursorstring–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").

NameTypeReqDescription
airportstring–Airport slug for a per-airport breakdown.
speciesstring–Species slug for a per-species breakdown.
NameTypeReqDescription
dataobjectyesglobal totals, or the breakdown for one airport or species

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http com-himaxym-flightfinder-aviation-safety 'https://himaxym.com/mcp'
Common questions

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 87 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 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the FlightFinder Aviation Safety Data MCP server?

VerifyMCP ran 13 checks on FlightFinder Aviation Safety Data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.