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.

Luchtmeetnet

NPM · @PIPEWORX/MCP-LUCHTMEETNET · 2 COMPONENTS

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

+3 this week 82 Trust /100

Last scanned (13 hours ago)

Scores higher than 72% of npm servers

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-luchtmeetnet). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 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.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 1 Nov 26 +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.

  • 30 Oct 26 +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.

  • 29 Oct 26 79

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-luchtmeetnet@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-luchtmeetnet
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-luchtmeetnet/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3649729732
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:8badd3812c499b9c0f35ad9c3467b8d2183f411d0f0a2b3801b367dcb54ca8c02815eff7de1f4e7299393368a3aa2322f0ba9cb18668d39569dc4d5d0

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~589 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
luchtmeetnet_air_quality_index ~157

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" })

NameTypeReqDescription
stationstringyesStation number like "NL49012", or a place name like "Amsterdam", "Rotterdam", "Utrecht"

No output schema declared.

No examples provided.

luchtmeetnet_measurements ~232

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

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

No output schema declared.

No examples provided.

luchtmeetnet_stations ~200

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" })

NameTypeReqDescription
latitudenumber–Latitude — together with longitude, returns stations sorted by distance (nearest first)
limitnumber–Max stations to return, 1-102 (default 10)
longitudenumber–Longitude — together with latitude, returns stations sorted by distance (nearest first)
searchstring–Text filter on station location, e.g. "Amsterdam", "Rotterdam", "Utrecht", "Van Diemenstraat"

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-luchtmeetnet

# add to Claude Code
claude mcp add pipeworx-io-luchtmeetnet -- npx -y @pipeworx/mcp-luchtmeetnet
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.