nl.getapi/mcp
GetApi MCP
Is the nl.getapi/mcp MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-12.
Nederlandse overheids- en registerdata via MCP: KVK, BAG, energielabel, kenteken, DSO en meer.
alive probed 2026-11-15 · unchanged since 2026-11-12 · HTTP 200
- Endpoint
- https://api.getapi.nl/mcp (streamable-http)
- Host
- api.getapi.nl
- Protocol
- 2025-06-18
- Reports itself as
- GetApi MCP 1.0.0
- Capabilities
- tools
- Instructions
- 409 characters
- Of a 1M window
- ≈ 0.6 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: tools.21.custom.input_schema.properties: Property keys should match pattern '^[a-zA-Z0-9_.-]{1,64}$'. The estimate stands in.
- Repository
- https://github.com/GetApiNL/mcp-server
- Registry
- active, updated 2026-10-16 · registry entry
- Changes
- 11 recorded, reachable in 11 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| property.woz.waarde | 673 | 11 % |
| rdw.vehicle | 421 | 7 % |
| property.pandgegevens | 267 | 4 % |
| ndw.laadpunten | 237 | 4 % |
| property.pandgegevens.lite | 236 | 4 % |
Compare this server with others.
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-12 12:09 | alive | 743 ms | 33 | 6.4k | |
| 2026-11-11 11:51 | alive | 766 ms | 33 | 6.4k | |
| 2026-11-10 12:07 | alive | 663 ms | 33 | 6.4k | |
| 2026-11-06 11:50 | alive | 1.4 s | 30 | 5.8k | |
| 2026-11-03 11:43 | alive | 1.3 s | 30 | 5.5k | |
| 2026-10-28 10:20 | alive | 977 ms | 30 | 5.5k | |
| 2026-10-27 09:37 | alive | 1.2 s | 34 | 6.5k | |
| 2026-10-25 08:58 | alive | 665 ms | 28 | 5.5k | |
| 2026-10-19 17:29 | alive | 1.7 s | 31 | 6.2k | |
| 2026-10-18 08:51 | alive | 2.1 s | 31 | 6.3k | |
| 2026-10-17 08:22 | alive | 1.3 s | 30 | 5.9k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The Anthropic count_tokens endpoint refused the tool schemas (tools.21.custom.input_schema.properties: Property keys should match pattern '^[a-zA-Z0-9_.-]{1,64}$'). A client that validates schemas can refuse them too.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.