# Luchtmeetnet (npm · @pipeworx/mcp-luchtmeetnet)

Luchtmeetnet MCP — official Netherlands air quality (RIVM Luchtmeetnet, api.luchtmeetnet.nl)

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 84/100, [markdown](https://verifymcp.io/servers/pipeworx-io-luchtmeetnet/luchtmeetnet-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-luchtmeetnet/luchtmeetnet-mcp)
- npm · `@pipeworx/mcp-luchtmeetnet`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-luchtmeetnet/pipeworx-mcp-luchtmeetnet.md), [page](https://verifymcp.io/servers/pipeworx-io-luchtmeetnet/pipeworx-mcp-luchtmeetnet)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-luchtmeetnet`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-luchtmeetnet).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 644 tokens (~214/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**: 23/100
  - Stability observed for 7 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**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Luchtmeetnet MCP server?

Luchtmeetnet runs locally as an npm package, launched with npx -y @pipeworx/mcp-luchtmeetnet. 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 pipeworx-io-luchtmeetnet -- npx -y @pipeworx/mcp-luchtmeetnet
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-luchtmeetnet": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-luchtmeetnet"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-luchtmeetnet": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-luchtmeetnet"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-luchtmeetnet -- npx -y @pipeworx/mcp-luchtmeetnet
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-luchtmeetnet": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-luchtmeetnet"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-luchtmeetnet --command npx --arg -y --arg @pipeworx/mcp-luchtmeetnet
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-luchtmeetnet:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-luchtmeetnet"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-luchtmeetnet": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-luchtmeetnet"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-luchtmeetnet -t stdio -c npx -a -y @pipeworx/mcp-luchtmeetnet
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-luchtmeetnet": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-luchtmeetnet"
      ]
    }
  }
}
```

## 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-11-04 (score 82, +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-11-03 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 66, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 81, +1)

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

### 2026-10-30 (score 80, +1)

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

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (3)

### `luchtmeetnet_stations` (~200 tokens)

List and search official Netherlands air quality measuring stations (RIVM Luchtmeetnet). Filter by place or station name (Amsterdam, Rotterdam, Utrecht, Den Haag...), or pass latitude/longitude to get the nearest stations with distance. Returns station number (e.g. "NL49012"), location, and coordinates — the station number feeds luchtmeetnet_measurements and luchtmeetnet_air_quality_index. Example: luchtmeetnet_stations({ search: "Amsterdam" })

Input parameters:

- `latitude` (number): Latitude — together with longitude, returns stations sorted by distance (nearest first)
- `limit` (number): Max stations to return, 1-102 (default 10)
- `longitude` (number): Longitude — together with latitude, returns stations sorted by distance (nearest first)
- `search` (string): Text filter on station location, e.g. "Amsterdam", "Rotterdam", "Utrecht", "Van Diemenstraat"

### `luchtmeetnet_measurements` (~232 tokens)

Get recent air pollution measurements from a Netherlands (RIVM Luchtmeetnet) measuring station: NO2, PM10, PM2.5 (PM25), ozone (O3), SO2, CO and more, hourly values in µg/m³. Station can be an NL number ("NL49012") or a Dutch place name ("Amsterdam", "Rotterdam") — the first matching station is used. Example: luchtmeetnet_measurements({ station: "Amsterdam", pollutant: "NO2", hours: 6 })

Input parameters:

- `hours` (number): How many hours back to fetch, 1-168 (default 6). Data updates hourly
- `pollutant` (string): Pollutant formula: NO2, PM10, PM25 (PM2.5), O3, NO, SO2, CO, NH3, C6H6... Omit for all pollutants the station measures
- `station` (string, required): Station number like "NL49012", or a place/station name like "Amsterdam" or "Rotterdam-Pleinweg"

### `luchtmeetnet_air_quality_index` (~157 tokens)

Get the official Dutch air quality index (LKI, Luchtkwaliteitsindex) for a Netherlands station or place — a 1-11 scale computed by RIVM from PM10, ozone and NO2: 1-3 good (goed), 4-6 moderate (matig), 7-8 poor (onvoldoende), 9-10 bad (slecht), 11 very bad (zeer slecht). Answers "how is the air quality in Amsterdam right now". Example: luchtmeetnet_air_quality_index({ station: "Rotterdam" })

Input parameters:

- `station` (string, required): Station number like "NL49012", or a place name like "Amsterdam", "Rotterdam", "Utrecht"

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-luchtmeetnet/pipeworx-mcp-luchtmeetnet#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 66
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79

## Common questions

### What is the Luchtmeetnet MCP server?

Luchtmeetnet is an MCP server listed in the public MCP registry as io.github.pipeworx-io/luchtmeetnet. Luchtmeetnet MCP, official Netherlands air quality (RIVM Luchtmeetnet, api.luchtmeetnet.nl). This page covers its npm package (@pipeworx/mcp-luchtmeetnet).

### Is the Luchtmeetnet MCP server safe to use?

Luchtmeetnet scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Luchtmeetnet MCP server expose?

Luchtmeetnet exposes 3 tools: luchtmeetnet_stations, luchtmeetnet_measurements, luchtmeetnet_air_quality_index. Their descriptions and schemas cost roughly 589 tokens of context every time the server is loaded.

### Is the Luchtmeetnet MCP server still maintained?

Luchtmeetnet is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Luchtmeetnet MCP server under?

Luchtmeetnet declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-luchtmeetnet
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-luchtmeetnet
- Repository: https://github.com/pipeworx-io/mcp-luchtmeetnet
- Website: https://pipeworx.io/packs/luchtmeetnet
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-luchtmeetnet/pipeworx-mcp-luchtmeetnet.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-luchtmeetnet/pipeworx-mcp-luchtmeetnet.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-luchtmeetnet/pipeworx-mcp-luchtmeetnet