Remote MCP · Endpoint
Schiphol Herrie MCP server
Yes, as of 2 hours ago: the server returned an HTTP error.
DownLast checked 2 hours ago
Server URL
https://schipholherrie.nl/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- nl.schipholherrie/schipholherrie
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 55.6% from 18 checks
- Described by its publisher as
- Aircraft noise over the Netherlands: what flies over you and how loud, and report a noisy flight
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 3 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 8 days ago | Failed - the server returned an HTTP error | — |
| 11 days ago | Handshake completed | 306 ms |
| 13 days ago | Handshake completed | 312 ms |
| 16 days ago | Handshake completed | 338 ms |
| 18 days ago | Handshake completed | 330 ms |
| 20 days ago | Handshake completed | 300 ms |
| 22 days ago | Handshake completed | 322 ms |
| 24 days ago | Handshake completed | 334 ms |
| 26 days ago | Handshake completed | 305 ms |
| 27 days ago | Handshake completed | 352 ms |
| 29 days ago | Handshake completed | 316 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 21 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Schiphol Herrie and makes no claim about it beyond what these checks measured.