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.

Stadiq

NPM · STADIQ-MCP

Road works, De Lijn transit disruptions, air quality and briefings for Flanders and Brussels.

Available components

+33 this week 66 Trust /100

Last scanned (19 hours ago)

Scores higher than 37% of npm servers

Category Maps and Location

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 Security98
  • 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
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 407 tokens (~101/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 4 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 15 Oct 26 +33
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
  • 11 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 9 Oct 26 18

    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 18 Oct 2026 · Analysed npm/stadiq-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~407 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
stadiq_air_quality ~123

Latest NO2/PM reading from the nearest IRCELINE station for a point, how it compares to WHO and EU limits, and whether the point sits inside the Antwerp low-emission zone. Measured values only.

NameTypeReqDescription
latnumber–Latitude of the point. Must be inside Flanders or Brussels. Pair with lng.
lngnumber–Longitude of the point. Pair with lat.
locationIdstring–Id of one of the account's saved locations, from stadiq_locations. Use instead of lat/lng.

No output schema declared.

No examples provided.

stadiq_briefing ~127

Situational briefing for a point: risk level, key facts, the best and worst windows in the next 24 hours, and the next rush-hour NO2 peak. Deterministic — computed from live data, not generated prose.

NameTypeReqDescription
latnumber–Latitude of the point. Must be inside Flanders or Brussels. Pair with lng.
lngnumber–Longitude of the point. Pair with lat.
locationIdstring–Id of one of the account's saved locations, from stadiq_locations. Use instead of lat/lng.

No output schema declared.

No examples provided.

stadiq_disruptions ~115

Road works within 2 km of a point and De Lijn transit disruptions affecting it, plus counts of active, planned and imminent works. Covers Flanders and Brussels only.

NameTypeReqDescription
latnumber–Latitude of the point. Must be inside Flanders or Brussels. Pair with lng.
lngnumber–Longitude of the point. Pair with lat.
locationIdstring–Id of one of the account's saved locations, from stadiq_locations. Use instead of lat/lng.

No output schema declared.

No examples provided.

stadiq_locations ~42

List the locations on the Stadiq account behind this API key, with their ids and coordinates. Use the returned id as locationId for the other tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Stadiq MCP server?

Stadiq runs locally as an npm package, launched with npx -y stadiq-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · stadiq-mcp

# add to Claude Code
claude mcp add snenenenenenene-stadiq -- npx -y stadiq-mcp
Common questions

What is the Stadiq MCP server?

Stadiq is an MCP server listed in the public MCP registry as io.github.snenenenenenene/stadiq. Road works, De Lijn transit disruptions, air quality and briefings for Flanders and Brussels. This page covers its npm package (stadiq-mcp).

Is the Stadiq MCP server safe to use?

Stadiq scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. 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 Stadiq MCP server expose?

Stadiq exposes 4 tools: stadiq_locations, stadiq_disruptions, stadiq_air_quality, stadiq_briefing. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.

Is the Stadiq MCP server still maintained?

Stadiq is still listed as active in the MCP registry. We last reached this channel on 18 October 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 Stadiq MCP server under?

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