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 · SCANNED SEP 25

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

+4 this week 76 Trust /100
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
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 601 tokens (~200/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
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'
// .cursor/mcp.json
{
  "mcpServers": {
    "nl-schipholherrie-schipholherrie": {
      "url": "https://schipholherrie.nl/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nl-schipholherrie-schipholherrie": {
      "type": "http",
      "url": "https://schipholherrie.nl/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.nl-schipholherrie-schipholherrie]
url = "https://schipholherrie.nl/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nl-schipholherrie-schipholherrie": {
      "type": "remote",
      "url": "https://schipholherrie.nl/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nl-schipholherrie-schipholherrie --url 'https://schipholherrie.nl/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  nl-schipholherrie-schipholherrie:
    url: "https://schipholherrie.nl/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nl-schipholherrie-schipholherrie": {
      "Transport": "http",
      "Url": "https://schipholherrie.nl/mcp"
    }
  }
}
# add to Vellum
assistant mcp add nl-schipholherrie-schipholherrie -t streamable-http -u 'https://schipholherrie.nl/mcp'
// mcp.json
{
  "mcpServers": {
    "nl-schipholherrie-schipholherrie": {
      "type": "http",
      "url": "https://schipholherrie.nl/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 15 Sept 26 71

    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 25 Sept 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 1 Sept 2026 30 Nov 2026 ECDSA 256 ECDSA-SHA256 c7b0b65c1265a4c513c09f0fde5fcc69
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. present 17153 13 Verified
schipholherrie.nl. 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=15552000
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://tile.openstreetmap.org https://server.arcgisonline.com https://*.tile.opentopomap.org https://*.tile.openstreetmap.fr https://*.tile-cyclosm.openstreetmap.fr; connect-src 'self'; font-src 'self' data:; manifest-src 'self'; worker-src 'self' blob:; frame-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(self), camera=(), microphone=(), payment=(), usb=()

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 Verified 200
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.

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 76 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?

No. We connected to Schiphol Herrie without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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