# Schiphol Herrie (remote · schipholherrie.nl)

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

- Trust score: 76/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `schipholherrie.nl`: 76/100 (this document), [markdown](https://verifymcp.io/servers/nl-schipholherrie-schipholherrie/schipholherrie.md), [page](https://verifymcp.io/servers/nl-schipholherrie-schipholherrie/schipholherrie)

## Channel facts

- Endpoint: `https://schipholherrie.nl/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http nl-schipholherrie-schipholherrie 'https://schipholherrie.nl/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nl-schipholherrie-schipholherrie": {
      "url": "https://schipholherrie.nl/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nl-schipholherrie-schipholherrie": {
      "type": "http",
      "url": "https://schipholherrie.nl/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nl-schipholherrie-schipholherrie --url 'https://schipholherrie.nl/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nl-schipholherrie-schipholherrie:
    url: "https://schipholherrie.nl/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nl-schipholherrie-schipholherrie": {
      "Transport": "http",
      "Url": "https://schipholherrie.nl/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nl-schipholherrie-schipholherrie -t streamable-http -u 'https://schipholherrie.nl/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 75, +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.

### 2026-09-21 (score 74, +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.

### 2026-09-19 (score 73, +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.

### 2026-09-17 (score 72, +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.

### 2026-09-16 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-15 (score 71)

First indexed and scored.

## MCP tools (3)

### `wat_vliegt_over` (~145 tokens)

Wat vliegt er over

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?".

Input parameters:

- `lat` (number, required): Latitude of the listener (WGS84), within the Netherlands
- `lon` (number, required): Longitude of the listener
- `min_db` (number): Only aircraft at or above this modelled level; default 45

### `meld_herrie` (~287 tokens)

Meld herrie

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.

Input parameters:

- `callsign` (string): Callsign such as KLM1234 or TRA5X, when the hex is unknown
- `db` (number): Level heard or measured in dB(A), if known
- `hex` (string): ICAO 24-bit address of the aircraft, 6 hex characters (from wat_vliegt_over)
- `lat` (number, required): Latitude where the noise was heard, within the Netherlands (stored rounded to ~1 km)
- `lon` (number, required): Longitude where the noise was heard
- `melder` (string): 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.

### `top_meldingen` (~51 tokens)

Meest gemelde vluchten

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nl-schipholherrie-schipholherrie/schipholherrie#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 75
- 2026-09-23: 75
- 2026-09-22: 74
- 2026-09-21: 74
- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72
- 2026-09-17: 72
- 2026-09-16: 71
- 2026-09-15: 71

## 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.

## Links

- Remote endpoint: https://schipholherrie.nl/mcp
- Website: https://schipholherrie.nl/api.md
- Changelog RSS feed: https://verifymcp.io/servers/nl-schipholherrie-schipholherrie/schipholherrie.xml
- Changelog JSON feed: https://verifymcp.io/servers/nl-schipholherrie-schipholherrie/schipholherrie.json
- HTML version of this page: https://verifymcp.io/servers/nl-schipholherrie-schipholherrie/schipholherrie