# de.fluvigil/pegel (remote · fluvigil.de)

German and Swiss river gauges, groundwater and flood levels from ten official sources

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `fluvigil.de`: 81/100 (this document), [markdown](https://verifymcp.io/servers/de-fluvigil-pegel/fluvigil.md), [page](https://verifymcp.io/servers/de-fluvigil-pegel/fluvigil)

## Channel facts

- Endpoint: `https://fluvigil.de/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 637 tokens (~106/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http de-fluvigil-pegel 'https://fluvigil.de/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "de-fluvigil-pegel": {
      "url": "https://fluvigil.de/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "de-fluvigil-pegel": {
      "type": "http",
      "url": "https://fluvigil.de/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.de-fluvigil-pegel]
url = "https://fluvigil.de/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-fluvigil-pegel": {
      "type": "remote",
      "url": "https://fluvigil.de/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add de-fluvigil-pegel --url 'https://fluvigil.de/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  de-fluvigil-pegel:
    url: "https://fluvigil.de/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "de-fluvigil-pegel": {
      "Transport": "http",
      "Url": "https://fluvigil.de/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add de-fluvigil-pegel -t streamable-http -u 'https://fluvigil.de/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 81, +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.

### 2026-09-17 (score 80, +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.

### 2026-09-15 (score 79, +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.

### 2026-09-13 (score 78, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-12 (score 77, +41)

- [security improvement] Transport: unverified → pass
- [security improvement] 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.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] 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

### 2026-09-10 (score 36)

First indexed and scored.

## MCP tools (6)

### `search_stations` (~122 tokens)

Pegel suchen

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.

Input parameters:

- `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"

Output parameters:

- `note` (string): Present when the result was capped
- `stations` (array)
- `totalMatches` (number): Matches before the result cap

### `get_flood_situation` (~59 tokens)

Hochwasserlage

Current flood situation: stations with an active LHP flood class (1 small … 4 very large), optionally per federal state.

Input parameters:

- `federalState` (string): ISO 3166-2 code, e.g. DE-BY

Output parameters:

- `countByClass` (object): Station count per flood class name
- `stations` (array)
- `stationsWithFlood` (number)

### `get_station` (~77 tokens)

Pegel-Stammdaten

Master data of one station: measurement type, current value with its unit, thresholds (MNW/MHW, alert marks, as stored valueCentimeters), flood class, coordinates.

Input parameters:

- `stationId` (string, required): Namespaced station id, e.g. "pegelonline:<uuid>" or "lhp:BY_10026301"

Output parameters:

- `floodWarning`: The river section warning this gauge inherits; it describes the reach, not the gauge
- `id` (string)
- `latestMeasuredAt`
- `latestValue`: Latest level, in `unit`
- `latestValueCentimeters`
- `latitude` (number)
- `longitude` (number)
- `measurementType` (string): river | groundwater | sea_level | reservoir
- `name` (string)
- `thresholds` (array)
- `unit` (string)
- `valueDivisor` (number): Divide any valueCentimeters by this to read it in `unit`
- `water`

### `get_readings` (~220 tokens)

Messreihe

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.

Input parameters:

- `from` (string): ISO 8601 start, e.g. 2026-06-01T00:00:00Z
- `stationId` (string, required): 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)

Output parameters:

- `count` (number)
- `discharge` (array): Discharge series, m³/s
- `note` (string): Present when the series was downsampled
- `readings` (array): Level series as stored valueCentimeters
- `stationId` (string)
- `summary`: 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

### `get_weather` (~56 tokens)

Wettervorhersage am Pegel

Daily weather forecast at the station coordinate (DWD data via Bright Sky).

Input parameters:

- `stationId` (string, required): Namespaced station id, e.g. "pegelonline:<uuid>" or "lhp:BY_10026301"

Output parameters:

- `attribution` (string)
- `available` (boolean): False when the forecast provider is unreachable
- `daily`
- `stationId` (string)
- `stationName` (string)

### `get_forecast` (~103 tokens)

Wasserstandsvorhersage

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.

Input parameters:

- `horizonHours` (number): Hours ahead, default 72, capped at 240
- `stationId` (string, required): Namespaced station id, e.g. "lhp:RP_2640010"

Output parameters:

- `count` (number)
- `generatedAt`: Model run time; null when none was published
- `horizonHours` (number)
- `note` (string)
- `points` (array)
- `source`
- `stationId` (string)
- `unit` (string)
- `valueDivisor` (number): Divide valueCentimeters by this to read it in `unit`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/de-fluvigil-pegel/fluvigil#diagnostics

## Score history

- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 78
- 2026-09-13: 78
- 2026-09-12: 77
- 2026-09-11: 36
- 2026-09-10: 36

## Common questions

### 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.

## Links

- Remote endpoint: https://fluvigil.de/mcp
- Authorisation metadata: https://fluvigil.de/.well-known/oauth-protected-resource/mcp
- Website: https://fluvigil.de/mcp
- Changelog RSS feed: https://verifymcp.io/servers/de-fluvigil-pegel/fluvigil.xml
- Changelog JSON feed: https://verifymcp.io/servers/de-fluvigil-pegel/fluvigil.json
- HTML version of this page: https://verifymcp.io/servers/de-fluvigil-pegel/fluvigil