mcp-belgium
NPM · MCP-BELGIUM
Single MCP server for Belgian public transport, statistics, open data, and geospatial services.
Available components
Last scanned (22 hours ago)
Scores higher than 69% of npm servers
Category Maps and Location
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
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
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 →
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 →
urban_get_features ~83
Fetch GeoJSON features from an urban.brussels WFS layer.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | – | Optional bounding box as minX,minY,maxX,maxY |
| count | number | – | Maximum number of features to return |
| cqlFilter | string | – | Optional GeoServer CQL filter |
| typeName | string | yes | Exact WFS feature type name |
No output schema declared.
No examples provided.
urban_get_municipalities_boundaries ~42
Fetch Brussels municipality boundaries from the urban.brussels public WFS endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Maximum number of municipality features to return |
No output schema declared.
No examples provided.
urban_list_feature_types ~50
List public urban.brussels WFS feature types.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of feature types to return |
| query | string | – | Optional text filter on feature type name or title |
No output schema declared.
No examples provided.
urbis_build_map_url ~150
Build a public URBIS WMS GetMap URL for a layer and bounding box.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | yes | Bounding box as minX,minY,maxX,maxY |
| crs | string | – | Coordinate reference system |
| format | string | – | Requested WMS image format |
| height | number | – | Map image height in pixels |
| layerName | string | yes | Exact WMS layer name |
| service | string | yes | Which public URBIS WMS service to use |
| styles | string | – | Optional WMS style name |
| transparent | boolean | – | Whether the output image should be transparent |
| width | number | – | Map image width in pixels |
No output schema declared.
No examples provided.
urbis_get_layer ~53
Get metadata for a specific public URBIS WMS layer.
| Name | Type | Req | Description |
|---|---|---|---|
| layerName | string | yes | Exact WMS layer name |
| service | string | yes | Which public URBIS WMS service to inspect |
No output schema declared.
No examples provided.
urbis_list_layers ~70
List public URBIS WMS layers for the vector or raster service.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of layers to return |
| query | string | – | Optional text filter on layer name or title |
| service | string | yes | Which public URBIS WMS service to inspect |
No output schema declared.
No examples provided.
wallonia_geo_get_service ~48
Get metadata for a specific Wallonia GeoServices ArcGIS MapServer service.
| Name | Type | Req | Description |
|---|---|---|---|
| servicePath | string | yes | Service path, e.g. MOBILITE/AOT_ARRETTEC |
No output schema declared.
No examples provided.
wallonia_geo_list_folders ~23
List top-level folders published by Wallonia GeoServices.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wallonia_geo_list_services ~42
List ArcGIS REST services published in a Wallonia GeoServices folder.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Optional folder name, e.g. MOBILITE |
No output schema declared.
No examples provided.
wallonia_geo_query_layer ~112
Query features from a Wallonia GeoServices ArcGIS feature layer.
| Name | Type | Req | Description |
|---|---|---|---|
| layerId | number | yes | Numeric ArcGIS layer identifier |
| limit | number | – | Maximum number of records to return |
| outFields | string | – | Comma-separated fields or * |
| returnGeometry | boolean | – | Whether to include geometries in the response |
| servicePath | string | yes | Service path, e.g. MOBILITE/AOT_ARRETTEC |
| where | string | – | ArcGIS where clause |
No output schema declared.
No examples provided.
wallonia_get_dataset ~29
Get metadata for a Walloon open dataset.
| Name | Type | Req | Description |
|---|---|---|---|
| datasetId | string | yes | Dataset identifier |
No output schema declared.
No examples provided.
wallonia_get_records ~55
Get records from a Walloon open dataset.
| Name | Type | Req | Description |
|---|---|---|---|
| datasetId | string | yes | Dataset identifier |
| limit | number | – | Maximum number of records to return |
| where | string | – | Optional OpenDataSoft where clause |
No output schema declared.
No examples provided.
wallonia_search_datasets ~39
Search Walloon open datasets.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query |
| rows | number | – | Maximum number of datasets to return |
No output schema declared.
No examples provided.
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
claude mcp add lacausecrypto-mcp-belgium -- npx -y mcp-belgium
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.