Geo-Insights Environmental Data
REMOTE · MCP.GEO-INSIGHTS.NL
Dutch environmental data + BGI climate adaptation: 12 tools, 44 measures, 35 parameters. No auth.
Available components
Last scanned (16 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 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
- Context-footprint check failed: tool/resource definitions use about 2174 tokens (~155/item across 14 items; 12 tools + 2 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
- Tool “rank_measures” rewrote its description, which is the text the model reads security
- 15 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 70
First indexed and scored.
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 21 Nov 2026 · Probed https://mcp.geo-insights.nl/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.geo-insights.nl | CN=YE1,O=Let's Encrypt,C=US | 13 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 60d38e795ee38a49cd62972d36a19c7cc17 |
| SANs: mcp.geo-insights.nl | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.geo-insights.nl. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| nl. | DS published | 17153 | 13 | Verified |
| geo-insights.nl. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.geo-insights.nl/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.geo-insights.nl/mcp | HTTPS enforced | 308 | https://mcp.geo-insights.nl/mcp |
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 →
compare_measures Compare BGI Measures ~105
Side-by-side comparison of 2-5 BGI measures. Args: measure_slugs: List of 2-5 measure slugs (e.g. ["green-roof", "bioswale"]). Use search_bgi_measures to find valid slugs. Returns aligned comparison with goal scores, key performance parameters (retention, cooling, infiltration), costs, maintenance level, and scale.
| Name | Type | Req | Description |
|---|---|---|---|
| measure_slugs | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| last_updated | – | – | – |
| measures | array | yes | – |
No examples provided.
get_context_summary Get Environmental Context for Location ~116
Get environmental and socioeconomic context for a location in the Netherlands. Returns the neighborhood (buurt), municipality, population density, green space accessibility, health indicators, and livability scores. Args: lat: Latitude in WGS84 (e.g. 51.92 for Rotterdam) lon: Longitude in WGS84 (e.g. 4.47 for Rotterdam) Useful for understanding the local context before recommending BGI measures.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| avg_income | – | – | – |
| buurt_code | – | – | – |
| buurt_name | – | – | – |
| dist_green_km | – | – | – |
| dist_park_km | – | – | – |
| dist_water_km | – | – | – |
| gemeente_code | – | – | – |
| gemeente_name | – | – | – |
| good_health_pct | – | – | – |
| last_updated | – | – | – |
| leefbaarometer_fysiek | – | – | – |
| overweight_pct | – | – | – |
| population_density | – | – | – |
| wijk_code | – | – | – |
| woz_value | – | – | – |
No examples provided.
get_data_freshness Check Data Freshness ~144
Check how fresh the data is for each of the 10 sources. Returns sources with latest_observation timestamp, age_seconds, and a status classification: "fresh" (<1h), "stale" (<24h), "offline" (>24h), or "unreachable" (query failed for that source). Use this to verify data availability before querying readings, or to monitor source health. Individual source failures are reported per-source (status: "unreachable") rather than failing the entire call. This is also the server's health check — if this tool works, the server is operational.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| sources | array | yes | – |
No examples provided.
get_latest_readings Get Latest Environmental Readings ~284
Get the most recent environmental readings near a location. Args: lat: Latitude in WGS84 (e.g. 51.92 for Rotterdam) lon: Longitude in WGS84 (e.g. 4.47 for Rotterdam) radius_km: Search radius in kilometers (default 10, max 50) parameter: Optional filter by parameter name or alias (e.g. "pm2_5", "temperature", "pm25", "no2"). Use get_parameters() to see all valid names and aliases. limit: Maximum number of readings to return (default 100, max 500) Returns the single most recent reading per datastream within the radius. Each reading includes parameter, value, unit, timestamp, station_name, lat, lon, source, and source_attribution. For time-range queries, use get_readings_history instead. Invalid coordinates return an error with the valid ranges. An unrecognized parameter returns an error with the full list of valid names. If the data source is unreachable, returns cause (timeout, circuit_breaker_open) and retry_after_seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| limit | integer | – | – |
| lon | number | yes | – |
| parameter | – | – | – |
| radius_km | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| readings | array | yes | – |
No examples provided.
get_measure_detail Get BGI Measure Detail ~140
Get full detail for one BGI measure: performance, costs, scores, constraints. Args: measure_id_or_slug: UUID or slug (e.g. "green-roof", "bioswale", "permeable-paving"). Use search_bgi_measures to find valid slugs. Returns complete measure spec: description, all goal scores with confidence, performance parameters (retention, cooling, infiltration, etc.) with ranges and units, CAPEX/OPEX costs, site requirements, co-benefits, constraint compatibility, and evidence count.
| Name | Type | Req | Description |
|---|---|---|---|
| measure_id_or_slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_parameters List Environmental Parameters ~121
List all 35 available environmental parameters with units and aliases. Returns parameters with name, display_name, unit_display (human-readable), unit_ucum (formal UCUM code), definition_url (CF Conventions), and aliases. Use aliases in the 'parameter' argument of get_latest_readings or get_readings_history (e.g. "pm25", "temperature", "no2"). No FROST query needed — this is an instant in-memory lookup. Call it to discover valid parameter names before querying readings.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| parameters | array | yes | – |
No examples provided.
get_policy_requirements Get Municipality Policy Requirements ~149
Get BGI policy requirements for a Dutch municipality. Extracted from Officiele Bekendmakingen (official government publications). Shows what's required, recommended, or subsidized per gemeente. Args: gemeente_code_or_name: CBS code (e.g. "GM0599") or municipality name (e.g. "Rotterdam"). Use lookup_municipality to find codes. measure_slug: Optional — filter to one measure's requirements Returns requirements grouped by type (subsidy, regulation, obligation) with document titles, dates, amounts, and source URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| gemeente_code_or_name | string | yes | – |
| measure_slug | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| gemeente_code | string | yes | – |
| gemeente_name | string | yes | – |
| last_updated | – | – | – |
| requirements | array | yes | – |
No examples provided.
get_readings_history Get Historical Readings ~328
Get historical environmental readings near a location over a time range. Use this for trend analysis, comparisons, and time-series queries. Unlike get_latest_readings (which returns only the most recent value), this returns multiple observations per station within the time window. Args: lat: Latitude in WGS84 (e.g. 51.92 for Rotterdam) lon: Longitude in WGS84 (e.g. 4.47 for Rotterdam) parameter: Parameter name or alias (required — e.g. "temperature", "pm25", "no2"). Use get_parameters() for valid names. start: Start of time range in ISO 8601 (e.g. "2026-11-01T00:00:00Z") end: End of time range in ISO 8601 (default: now) radius_km: Search radius in kilometers (default 10, max 50) limit: Maximum readings per station (default 100, max 1000) Returns stations grouped by location, each with a time-ordered array of readings, plus parameter info and the actual time range covered. Invalid coordinates, unrecognized parameters, or unparseable dates return a structured error. Data source failures include cause and retry timing.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| lat | number | yes | – |
| limit | integer | – | – |
| lon | number | yes | – |
| parameter | string | yes | – |
| radius_km | number | – | – |
| start | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| parameter | string | yes | – |
| period_end | string | yes | – |
| period_start | string | yes | – |
| stations | array | yes | – |
| total_readings | integer | yes | – |
No examples provided.
list_sources List Environmental Data Sources ~146
List all environmental data sources with station counts and geographic coverage. Call this first to discover which data sources are available and how many stations each one has. Returns sources with name, station_count, datastream_count, and source_attribution (CC-BY license info). Sources include KNMI (weather), Luchtmeetnet (air quality), BRO (groundwater), Samen Meten (citizen science), Sensor.Community, and more. Typical workflow: list_sources → get_parameters → get_latest_readings. On error, returns a structured error with cause (timeout, circuit_breaker_open, connection_failed) and retry_after_seconds.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| sources | array | yes | – |
No examples provided.
lookup_municipality Lookup Municipality ~92
Find Dutch municipalities by name or province. Returns CBS codes needed for other tools (get_policy_requirements, rank_measures). All 342 Dutch municipalities are searchable. Args: name: Partial name match (e.g. "Rotter" finds Rotterdam) province: Filter by province name (e.g. "Zuid-Holland")
| Name | Type | Req | Description |
|---|---|---|---|
| name | – | – | – |
| province | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| municipalities | array | yes | – |
No examples provided.
rank_measures Rank BGI Measures for Municipality ~218
Rank BGI measures for a municipality using policy-weighted scoring. Combines goal alignment, cost-effectiveness, and maintenance into a single ranked list. Use different policy profiles to see how priorities change the ranking. Args: gemeente_code: CBS municipality code (e.g. "GM0599" for Rotterdam). Use lookup_municipality to find codes. goal: Optional boost for a specific goal (flood, heat, drought, biodiversity, social) policy_profile: Scoring profile — one of: Balanced, Flood-focused, Heat-focused, Drought-focused, Biodiversity-first, Cost-efficient (default: Balanced) limit: Max results (default 10, max 50) Premium tool — requires mcp:tools:premium scope when premium gating is enabled (MCP_PREMIUM_GATING=true).
| Name | Type | Req | Description |
|---|---|---|---|
| gemeente_code | string | yes | – |
| goal | – | – | – |
| limit | integer | – | – |
| policy_profile | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| gemeente_code | string | yes | – |
| gemeente_name | string | yes | – |
| last_updated | – | – | – |
| measures | array | yes | – |
| policy_profile | string | yes | – |
No examples provided.
search_bgi_measures Search BGI Measures ~168
Search the Blue-Green Infrastructure measure catalog (44 measures). All parameters are optional — call with no args to list all measures. Args: goal: Filter by climate goal: flood, heat, drought, biodiversity, social category: Filter by category: water_retention, heat_mitigation, surface_water, biodiversity keyword: Search in name, Dutch name, and description (e.g. "dak", "roof") limit: Max results (default 20, max 50) Returns measures with goal scores, category, scale, and maintenance level. Use get_measure_detail for full specs on a specific measure.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| goal | – | – | – |
| keyword | – | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| last_updated | – | – | – |
| measures | array | yes | – |
No examples provided.
How do I install the Geo-Insights Environmental Data MCP server?
Geo-Insights Environmental Data is a hosted endpoint at https://mcp.geo-insights.nl/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.geo-insights.nl
claude mcp add --transport http mathisvfr-environmental-data 'https://mcp.geo-insights.nl/mcp'
What is the Geo-Insights Environmental Data MCP server?
Geo-Insights Environmental Data is an MCP server listed in the public MCP registry as io.github.mathisvfr/environmental-data. Dutch environmental data + BGI climate adaptation: 12 tools, 44 measures, 35 parameters. No auth. This page covers its hosted endpoint (https://mcp.geo-insights.nl/mcp).
Is the Geo-Insights Environmental Data MCP server safe to use?
Geo-Insights Environmental Data scores 73 out of 100 on VerifyMCP. 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 Geo-Insights Environmental Data MCP server expose?
Geo-Insights Environmental Data exposes 12 tools: list_sources, get_parameters, get_latest_readings, get_readings_history, get_data_freshness, and 7 more. Their descriptions and schemas cost roughly 2,011 tokens of context every time the server is loaded.
Does the Geo-Insights Environmental Data MCP server require authentication?
No. We connected to Geo-Insights Environmental Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Geo-Insights Environmental Data MCP server still maintained?
Geo-Insights Environmental Data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Geo-Insights Environmental Data MCP server?
VerifyMCP ran 13 checks on Geo-Insights Environmental Data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.