de.fluvigil/pegel
REMOTE · FLUVIGIL.DE · SCANNED SEP 20
German and Swiss river gauges, groundwater and flood levels from ten official sources
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 637 tokens (~106/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
- 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the de.fluvigil/pegel MCP server?
de.fluvigil/pegel is a hosted endpoint at https://fluvigil.de/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 · fluvigil.de
claude mcp add --transport http de-fluvigil-pegel 'https://fluvigil.de/mcp'
{
"mcpServers": {
"de-fluvigil-pegel": {
"url": "https://fluvigil.de/mcp"
}
}
} {
"servers": {
"de-fluvigil-pegel": {
"type": "http",
"url": "https://fluvigil.de/mcp"
}
}
} [mcp_servers.de-fluvigil-pegel] url = "https://fluvigil.de/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"de-fluvigil-pegel": {
"type": "remote",
"url": "https://fluvigil.de/mcp",
"enabled": true
}
}
} openclaw mcp add de-fluvigil-pegel --url 'https://fluvigil.de/mcp' --transport streamable-http
mcp_servers:
de-fluvigil-pegel:
url: "https://fluvigil.de/mcp" {
"McpServers": {
"de-fluvigil-pegel": {
"Transport": "http",
"Url": "https://fluvigil.de/mcp"
}
}
} assistant mcp add de-fluvigil-pegel -t streamable-http -u 'https://fluvigil.de/mcp'
{
"mcpServers": {
"de-fluvigil-pegel": {
"type": "http",
"url": "https://fluvigil.de/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 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.
- 17 Sept 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.
- 15 Sept 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.
- 13 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Sept 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ 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
- First check of Tool coverage: 100 functional
- 10 Sept 26 36
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 20 Sept 2026 · Probed https://fluvigil.de/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fluvigil.de | CN=YE2,O=Let's Encrypt,C=US | 10 Aug 2026 | 8 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 610855afa4f3892807a2515f5cfb2e90275 |
| SANs: fluvigil.de | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 fluvigil.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| de. | present | 26755 | 8 | Verified |
| fluvigil.de. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fluvigil.de/mcp | Verified | 200 | |
| http (plaintext) | http://fluvigil.de/mcp | HTTPS enforced | 308 | https://fluvigil.de/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 →
get_flood_situation Hochwasserlage ~59
Current flood situation: stations with an active LHP flood class (1 small … 4 very large), optionally per federal state.
| Name | Type | Req | Description |
|---|---|---|---|
| federalState | string | – | ISO 3166-2 code, e.g. DE-BY |
| Name | Type | Req | Description |
|---|---|---|---|
| countByClass | object | yes | Station count per flood class name |
| stations | array | yes | – |
| stationsWithFlood | number | yes | – |
No examples provided.
get_forecast Wasserstandsvorhersage ~103
Newest published water-level forecast for a station: the median of the state agency model run, future points within the horizon. Only gauges whose state publishes numeric forecasts have one, so an empty result is normal. Indicative, not an official warning.
| Name | Type | Req | Description |
|---|---|---|---|
| horizonHours | number | – | Hours ahead, default 72, capped at 240 |
| stationId | string | yes | Namespaced station id, e.g. "lhp:RP_2640010" |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| generatedAt | – | yes | Model run time; null when none was published |
| horizonHours | number | yes | – |
| note | string | yes | – |
| points | array | yes | – |
| source | – | yes | – |
| stationId | string | yes | – |
| unit | string | yes | – |
| valueDivisor | number | yes | Divide valueCentimeters by this to read it in `unit` |
No examples provided.
get_readings Messreihe ~220
Time series for a station (downsampled to ≤200 points; history depth on this tier: last 90 days, default last 7 days). type "level" (default) → level series as stored valueCentimeters: centimetres above gauge zero for most gauges, but an elevation ×100 for groundwater wells and for gauges reporting an absolute elevation (Swiss gauges, the Neusiedler See) — divide by valueDivisor to read it in unit. type "discharge" → discharge Q in m³/s where the station provides it.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO 8601 start, e.g. 2026-06-01T00:00:00Z |
| stationId | string | yes | Namespaced station id, e.g. "pegelonline:<uuid>" or "lhp:BY_10026301" |
| to | string | – | ISO 8601 end, defaults to now |
| type | string | – | Series type: level (default) or discharge (m³/s) |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| discharge | array | – | Discharge series, m³/s |
| note | string | – | Present when the series was downsampled |
| readings | array | – | Level series as stored valueCentimeters |
| stationId | string | yes | – |
| summary | – | yes | Min and max (level: in unit) and latest point; null when empty |
| unit | string | – | Unit of a level series; absent for discharge |
| valueDivisor | number | – | Divide valueCentimeters by this to read in unit |
No examples provided.
get_station Pegel-Stammdaten ~77
Master data of one station: measurement type, current value with its unit, thresholds (MNW/MHW, alert marks, as stored valueCentimeters), flood class, coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| stationId | string | yes | Namespaced station id, e.g. "pegelonline:<uuid>" or "lhp:BY_10026301" |
| Name | Type | Req | Description |
|---|---|---|---|
| floodWarning | – | yes | The river section warning this gauge inherits; it describes the reach, not the gauge |
| id | string | yes | – |
| latestMeasuredAt | – | yes | – |
| latestValue | – | yes | Latest level, in `unit` |
| latestValueCentimeters | – | yes | – |
| latitude | number | yes | – |
| longitude | number | yes | – |
| measurementType | string | yes | river | groundwater | sea_level | reservoir |
| name | string | yes | – |
| thresholds | array | yes | – |
| unit | string | yes | – |
| valueDivisor | number | yes | Divide any valueCentimeters by this to read it in `unit` |
| water | – | yes | – |
No examples provided.
get_weather Wettervorhersage am Pegel ~56
Daily weather forecast at the station coordinate (DWD data via Bright Sky).
| Name | Type | Req | Description |
|---|---|---|---|
| stationId | string | yes | Namespaced station id, e.g. "pegelonline:<uuid>" or "lhp:BY_10026301" |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | – |
| available | boolean | yes | False when the forecast provider is unreachable |
| daily | – | yes | – |
| stationId | string | yes | – |
| stationName | string | yes | – |
No examples provided.
search_stations Pegel suchen ~122
Search stations in Germany and its neighbouring countries — river gauges, groundwater wells, reservoirs, coastal gauges — by name or water body, optionally filtered by region (a German federal state or a country code). latestValue is given in the station's unit.
| Name | Type | Req | Description |
|---|---|---|---|
| federalState | string | – | ISO 3166-2 code for a German state, e.g. DE-NW; CH, AT, CZ, LU or FR for a country |
| query | string | – | Station or water name, e.g. "Köln" or "Rhein" |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Present when the result was capped |
| stations | array | yes | – |
| totalMatches | number | yes | Matches before the result cap |
No examples provided.
What is the de.fluvigil/pegel MCP server?
de.fluvigil/pegel is an MCP server listed in the public MCP registry as de.fluvigil/pegel. German and Swiss river gauges, groundwater and flood levels from ten official sources. This page covers its hosted endpoint (https://fluvigil.de/mcp).
Is the de.fluvigil/pegel MCP server safe to use?
de.fluvigil/pegel scores 81 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 de.fluvigil/pegel MCP server expose?
de.fluvigil/pegel exposes 6 tools: search_stations, get_flood_situation, get_station, get_readings, get_weather, get_forecast. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.
Does the de.fluvigil/pegel MCP server require authentication?
Yes. de.fluvigil/pegel asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the de.fluvigil/pegel MCP server still maintained?
de.fluvigil/pegel is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.