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.

Schiphol Herrie

REMOTE · SCHIPHOLHERRIE.NL

Aircraft noise over the Netherlands: what flies over you and how loud, and report a noisy flight

0 this week 23 Trust /100

Last scanned (21 minutes ago)

Scores higher than 7% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Maps and Location

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 Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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.

  • 6 Nov 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
  • 27 Oct 26 −62
    • 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
  • 23 Oct 26 0
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Transport: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 22 Oct 26 0
    • 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
  • 15 Oct 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
  • 16 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
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 22 Nov 2026 · Probed https://schipholherrie.nl/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=schipholherrie.nl CN=WE1,O=Google Trust Services,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA256 504d10263d75292013d99f2fb17dc7c7
SANs: schipholherrie.nl, *.schipholherrie.nl
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 schipholherrie.nl. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
nl. DS published 17153 13 Verified
schipholherrie.nl. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 530
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://schipholherrie.nl/mcp HTTP error 530
http (plaintext) http://schipholherrie.nl/mcp HTTPS enforced 301 https://schipholherrie.nl/mcp
MCP tools · 3 exposed · ~483 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
meld_herrie ~287

Report an aircraft as noisy ("meld herrie") at a location, as a visitor does from the flight card on the live map. The report is anonymous and public in aggregate: it adds to that aircraft's badge on the map and to the day's and week's most-reported flights. Give the aircraft's hex (from wat_vliegt_over) or its callsign; without either, the loudest aircraft over the location right now is reported. One report per aircraft per two hours per reporter. This is not an official complaint; those go to BAS (bezoekbas.nl), see https://schipholherrie.nl/klacht.html.

NameTypeReqDescription
callsignstring–Callsign such as KLM1234 or TRA5X, when the hex is unknown
dbnumber–Level heard or measured in dB(A), if known
hexstring–ICAO 24-bit address of the aircraft, 6 hex characters (from wat_vliegt_over)
latnumberyesLatitude where the noise was heard, within the Netherlands (stored rounded to ~1 km)
lonnumberyesLongitude where the noise was heard
melderstring–Optional reporter id: 16-64 hex characters your agent keeps, so repeat reports from the same person are recognised across addresses. Only a hash is stored.

No output schema declared.

No examples provided.

top_meldingen ~51

The most-reported flights and airlines of today and of the last 7 days, and how many reports there are in total. Reports come from visitors of schipholherrie.nl and from this endpoint.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

wat_vliegt_over ~145

Aircraft currently over or near a location in the Netherlands, loudest first, with the modelled sound level at that spot in dB(A) (an estimate from ADS-B positions and a noise model, not a measurement; the real value can differ 5-10 dB). Use it to find the hex of the aircraft to report with meld_herrie, or to answer "what is that plane?".

NameTypeReqDescription
latnumberyesLatitude of the listener (WGS84), within the Netherlands
lonnumberyesLongitude of the listener
min_dbnumber–Only aircraft at or above this modelled level; default 45

No output schema declared.

No examples provided.

Install

How do I install the Schiphol Herrie MCP server?

Schiphol Herrie is a hosted endpoint at https://schipholherrie.nl/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 · schipholherrie.nl

# add to Claude Code
claude mcp add --transport http nl-schipholherrie-schipholherrie 'https://schipholherrie.nl/mcp'
Common questions

What is the Schiphol Herrie MCP server?

Schiphol Herrie is an MCP server listed in the public MCP registry as nl.schipholherrie/schipholherrie. Aircraft noise over the Netherlands: what flies over you and how loud, and report a noisy flight. This page covers its hosted endpoint (https://schipholherrie.nl/mcp).

Is the Schiphol Herrie MCP server safe to use?

Schiphol Herrie scores 23 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 Schiphol Herrie MCP server expose?

Schiphol Herrie exposes 3 tools: wat_vliegt_over, meld_herrie, top_meldingen. Their descriptions and schemas cost roughly 483 tokens of context every time the server is loaded.

Does the Schiphol Herrie MCP server require authentication?

Its publisher declares no required credentials for Schiphol Herrie. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Schiphol Herrie MCP server still maintained?

Schiphol Herrie is still listed as active in the MCP registry. We last reached this channel on 22 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 Schiphol Herrie MCP server?

VerifyMCP ran 5 checks on Schiphol Herrie, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Schiphol Herrie: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.