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.

mcp-belgium

NPM · MCP-BELGIUM

Single MCP server for Belgian public transport, statistics, open data, and geospatial services.

Available components

0 this week 81 Trust /100

Last scanned (21 hours ago)

Scores higher than 69% 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 39 of 120 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 197 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3817 tokens (~47/item across 81 items; 63 tools + 18 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 63 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 64 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
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
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 4 Nov 2026 · Analysed npm/mcp-belgium@1.0.4

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 120 packages
Packages resolved 120
Stale 39
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 63 exposed · ~3,345 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
airquality_get_belaqi ~46

Get the BelAQI air quality index for a location by using the nearest monitoring station.

NameTypeReqDescription
latitudenumberyesLatitude
longitudenumberyesLongitude

No output schema declared.

No examples provided.

airquality_get_current ~30

Get latest air quality measurements for a monitoring station.

NameTypeReqDescription
stationIdnumberyesStation ID

No output schema declared.

No examples provided.

airquality_get_timeseries ~52

Get historical measurements for a specific air quality timeseries.

NameTypeReqDescription
fromstringyesISO date
timeseriesIdnumberyesTimeseries ID
tostringyesISO date

No output schema declared.

No examples provided.

airquality_search_stations ~46

Search air quality monitoring stations near a location.

NameTypeReqDescription
latitudenumberyesLatitude
longitudenumberyesLongitude
radiusnumber–Radius in meters

No output schema declared.

No examples provided.

belgium_catalog_overview ~36

Get a structured overview of all Belgian domains aggregated by this server, including status, categories, resources, and recommended starting points.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

belgium_describe_domain ~66

Get the precise summary, tool list, upstream, authentication status, caveats, and data coverage for one Belgian domain aggregated by this server.

NameTypeReqDescription
domainstringyesExact Belgium domain identifier, for example irail, statbel, best-address, or urban-brussels

No output schema declared.

No examples provided.

belgium_list_domains ~155

List the Belgian domains aggregated by this server, optionally filtered by topic or restricted to domains that are live and require no API key. Deprecated domains (whose upstream API has been retired) are hidden by default.

NameTypeReqDescription
includeDeprecatedboolean–If true, also include domains whose upstream API has been retired and whose tools only return an upstream-unavailable error
includeToolsboolean–If true, include the exact tool names exposed by each returned domain
onlyPublicNoKeyboolean–If true, only return domains that are live and do not require an API key
querystring–Optional keyword filter across domain names, summaries, available data, use cases, notes, and tool names

No output schema declared.

No examples provided.

best_get_address ~34

Get a single Belgian address object by its BeST identifier URI.

NameTypeReqDescription
idstringyesBeST address identifier URI

No output schema declared.

No examples provided.

best_search_addresses ~152

Search Belgian addresses using the official BeST public address API.

NameTypeReqDescription
boxNumberstring–Optional box or apartment number
crsstring–Coordinate reference system
houseNumberstring–House number
limitnumber–Maximum number of addresses to return
municipalityNamestring–Municipality name, e.g. Bruxelles
pagenumber–Result page number
postCodestring–Belgian postal code
radiusnumber–Radius in meters when searching by coordinates
streetNamestring–Street name
xLongnumber–Longitude or X coordinate
yLatnumber–Latitude or Y coordinate

No output schema declared.

No examples provided.

best_search_municipalities ~78

Search Belgian municipalities in the official BeST address registry.

NameTypeReqDescription
limitnumber–Maximum number of municipalities to return
namestring–Municipality name
nisCodestring–Municipality NIS code
pagenumber–Result page number
postCodestring–Belgian postal code

No output schema declared.

No examples provided.

best_search_postal_infos ~70

Search Belgian postal information records in the official BeST address registry.

NameTypeReqDescription
limitnumber–Maximum number of postal info records to return
namestring–Postal locality name
pagenumber–Result page number
postCodestring–Belgian postal code

No output schema declared.

No examples provided.

best_search_streets ~99

Search Belgian street records in the official BeST address registry.

NameTypeReqDescription
limitnumber–Maximum number of streets to return
municipalityIdstring–Municipality identifier URI
municipalityNamestring–Municipality name
namestring–Street name
nisCodestring–Municipality NIS code
pagenumber–Result page number
postCodestring–Belgian postal code

No output schema declared.

No examples provided.

brussels_get_dataset ~29

Get metadata for a Brussels Region open dataset.

NameTypeReqDescription
datasetIdstringyesDataset identifier

No output schema declared.

No examples provided.

brussels_get_records ~55

Get records from a Brussels Region open dataset.

NameTypeReqDescription
datasetIdstringyesDataset identifier
limitnumber–Maximum number of records to return
wherestring–Optional OpenDataSoft where clause

No output schema declared.

No examples provided.

brussels_search_datasets ~39

Search Brussels Region open datasets.

NameTypeReqDescription
querystringyesSearch query
rowsnumber–Maximum number of datasets to return

No output schema declared.

No examples provided.

datagov_get_dataset ~38

Get full metadata and resource listings for a Belgian federal open dataset.

NameTypeReqDescription
datasetIdstringyesCKAN dataset ID or name

No output schema declared.

No examples provided.

datagov_get_resource ~38

Get the download URL and metadata for a specific Belgian federal CKAN resource.

NameTypeReqDescription
resourceIdstringyesCKAN resource ID

No output schema declared.

No examples provided.

datagov_list_organizations ~34

List Belgian public organizations publishing federal open data.

NameTypeReqDescription
limitnumber–Maximum number of organizations to return

No output schema declared.

No examples provided.

datagov_search_datasets ~68

Search Belgian federal open datasets published on data.gov.be.

NameTypeReqDescription
organizationstring–Publishing organization name or identifier
querystringyesSearch query
rowsnumber–Maximum number of datasets to return
tagsstring–Comma-separated tags

No output schema declared.

No examples provided.

flanders_get_dataset ~34

Get full metadata for a Flemish open dataset.

NameTypeReqDescription
datasetIdstringyesCKAN dataset ID or name

No output schema declared.

No examples provided.

flanders_list_organizations ~33

List Flemish public organizations publishing open data.

NameTypeReqDescription
limitnumber–Maximum number of organizations to return

No output schema declared.

No examples provided.

flanders_search_datasets ~68

Search Flemish open datasets published on the CKAN platform.

NameTypeReqDescription
organizationstring–Publishing organization name or identifier
querystringyesSearch query
rowsnumber–Maximum number of datasets to return
tagsstring–Comma-separated tags

No output schema declared.

No examples provided.

infrabel_get_dataset ~34

Get full metadata for an Infrabel open dataset.

NameTypeReqDescription
datasetIdstringyesOpenDataSoft dataset identifier

No output schema declared.

No examples provided.

infrabel_get_records ~64

Get records from an Infrabel dataset using the public ODS records endpoint.

NameTypeReqDescription
datasetIdstringyesOpenDataSoft dataset identifier
limitnumber–Maximum number of records to return
wherestring–Optional ODS where clause

No output schema declared.

No examples provided.

infrabel_search_datasets ~48

Search Infrabel open datasets published on the public OpenDataSoft portal.

NameTypeReqDescription
querystringyesSearch query
rowsnumber–Maximum number of datasets to return

No output schema declared.

No examples provided.

irail_get_connections ~92

Find train connections between two Belgian railway stations. Returns routes with departure/arrival times, platforms, delays, and transfers.

NameTypeReqDescription
datetimestring–ISO datetime, e.g. 2026-04-11T14:30
fromstringyesDeparture station name
timeSelstring–Search by departure or arrival time
tostringyesArrival station name

No output schema declared.

No examples provided.

irail_get_disturbances ~24

Get current Belgian railway disruptions, delays, and planned maintenance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

irail_get_liveboard ~60

Get real-time departures (or arrivals) at a Belgian railway station. Shows train number, destination, platform, and delay.

NameTypeReqDescription
arrivalsboolean–If true, show arrivals instead of departures
stationstringyesStation name

No output schema declared.

No examples provided.

irail_get_vehicle ~56

Get detailed stop information for a specific Belgian train. Shows all stops, arrival/departure times, delays, and platforms.

NameTypeReqDescription
vehicleIdstringyesVehicle ID, e.g. BE.NMBS.IC1832

No output schema declared.

No examples provided.

irail_search_stations ~39

Search Belgian railway stations by name. Returns station ID, name, and coordinates.

NameTypeReqDescription
querystringyesStation name or partial name

No output schema declared.

No examples provided.

kbo_get_enterprise ~43

Get full details for a Belgian enterprise by BCE number.

NameTypeReqDescription
enterpriseNumberstringyesBCE number, e.g. 0123.456.789

No output schema declared.

No examples provided.

kbo_search_by_activity ~39

Search Belgian enterprises by NACE activity code.

NameTypeReqDescription
naceCodestringyesNACE code, e.g. 62.010

No output schema declared.

No examples provided.

kbo_search_enterprise ~47

Search Belgian enterprises by enterprise name or BCE number.

NameTypeReqDescription
querystringyesEnterprise name or BCE number
typestring–Search by enterprise name or BCE number

No output schema declared.

No examples provided.

kmi_describe_feature_type ~48

Describe the schema of a KMI/IRM WFS feature type.

NameTypeReqDescription
typeNamestringyesExact WFS feature type name, e.g. aws:aws_station

No output schema declared.

No examples provided.

kmi_get_features ~95

Fetch GeoJSON features from a KMI/IRM WFS layer.

NameTypeReqDescription
bboxstring–Optional bounding box as minX,minY,maxX,maxY
countnumber–Maximum number of features to return
cqlFilterstring–Optional GeoServer CQL filter
typeNamestringyesExact WFS feature type name, e.g. aws:aws_1hour

No output schema declared.

No examples provided.

kmi_get_hourly_observations ~57

Get hourly weather observation features from the KMI/IRM WFS endpoint.

NameTypeReqDescription
countnumber–Maximum number of observations to return
stationCodenumber–Optional numeric station code to filter observations

No output schema declared.

No examples provided.

kmi_get_stations ~40

Get KMI/IRM automatic weather station features from the official WFS endpoint.

NameTypeReqDescription
countnumber–Maximum number of stations to return

No output schema declared.

No examples provided.

kmi_list_feature_types ~59

List public KMI/IRM WFS feature types available through the official GeoServer endpoint.

NameTypeReqDescription
limitnumber–Maximum number of feature types to return
querystring–Optional text filter on feature type name or title

No output schema declared.

No examples provided.

mobility_get_gtfs_feeds ~29

List GTFS static and GTFS-RT feed sources relevant to Belgian mobility planning.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mobility_get_operators ~21

List Belgian public transport operators participating in the mobility ecosystem.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mobility_plan_trip ~62

Plan an intermodal trip across Belgian public transport operators.

NameTypeReqDescription
datetimestring–ISO datetime, e.g. 2026-04-11T14:30
fromstringyesTrip origin
tostringyesTrip destination

No output schema declared.

No examples provided.

statbel_get_cpi ~29

Get Belgian consumer price index data from Statbel.

NameTypeReqDescription
yearnumber–Year

No output schema declared.

No examples provided.

statbel_get_employment ~27

Get Belgian employment statistics from Statbel.

NameTypeReqDescription
yearnumber–Year

No output schema declared.

No examples provided.

statbel_get_population ~42

Get Belgian population statistics from Statbel.

NameTypeReqDescription
regionstring–Belgium, Brussels, Flanders, Wallonia
yearnumber–Year

No output schema declared.

No examples provided.

statbel_search_datasets ~27

Search Statbel open data datasets.

NameTypeReqDescription
querystringyesSearch query

No output schema declared.

No examples provided.

stib_get_messages ~19

Get current STIB service messages and disruptions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

stib_get_route ~46

Get details for a STIB metro, tram, or bus line.

NameTypeReqDescription
lineIdstringyesLine number, e.g. 1, 81, 71

No output schema declared.

No examples provided.

stib_get_waiting_times ~36

Get real-time waiting times at a STIB stop.

NameTypeReqDescription
stopNamestringyesStop name or stop ID

No output schema declared.

No examples provided.

stib_search_stops ~28

Search STIB stops by name.

NameTypeReqDescription
querystringyesStop name query

No output schema declared.

No examples provided.

urban_describe_feature_type ~38

Describe the schema of an urban.brussels WFS feature type.

NameTypeReqDescription
typeNamestringyesExact WFS feature type name

No output schema declared.

No examples provided.

Install

How do I install the mcp-belgium server?

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

npm · mcp-belgium

# add to Claude Code
claude mcp add lacausecrypto-mcp-belgium -- npx -y mcp-belgium
Common questions

What is the mcp-belgium server?

mcp-belgium is listed in the public MCP registry as io.github.lacausecrypto/mcp-belgium. Single MCP server for Belgian public transport, statistics, open data, and geospatial services. This page covers its npm package (mcp-belgium).

Is the mcp-belgium server safe to use?

mcp-belgium scores 81 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 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 mcp-belgium server expose?

mcp-belgium exposes 63 tools: belgium_catalog_overview, belgium_describe_domain, belgium_list_domains, irail_search_stations, irail_get_connections, and 58 more. Their descriptions and schemas cost roughly 3,345 tokens of context every time the server is loaded.

Is the mcp-belgium server still maintained?

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

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