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.

de.fluvigil/pegel

REMOTE · FLUVIGIL.DE

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

Available components

0 this week 90 Trust /100

Last scanned (17 minutes ago)

Scores higher than 98% of remote servers

Reachable. Last reached 6 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 974 tokens (~162/item across 6 items; 6 tools + 0 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 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
  • 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
What we tested

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 →

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 14 Oct 26 0
    • “search_stations” added an optional parameter “waterClass” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 13 Oct 26 −2
    • Tool “get_flood_situation” rewrote its description, which is the text the model reads security
    • Tool “get_forecast” rewrote its description, which is the text the model reads security
    • Tool “get_readings” rewrote its description, which is the text the model reads security
    • Tool “get_station” rewrote its description, which is the text the model reads security
    • Tool “search_stations” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Schema quality: excellent → good functional
    • Server version: 1.1.0 → 1.2.0 functional
  • 12 Oct 26 +1
    • Stability: 0.97 → pass security
  • 10 Oct 26 +2

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 93. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 6 Nov 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 9 Oct 2026 7 Jan 2027 ECDSA 256 ECDSA-SHA384 59ecba456ffe60e5f7ad0d6be454e5bb700
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. DS published 26755 8 Verified
fluvigil.de. No DS 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
MCP tools · 6 exposed · ~974 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
get_flood_situation ~127

Current flood situation: stations with an active LHP flood class (1 small … 4 very large), optionally per federal state. Every result names the data provider in sourceNotice (search and flood situation: sourceNotices, keyed by sourceNoticeId); show that notice with any value, class or forecast you pass on, and the licence terms of the API require it.

NameTypeReqDescription
federalStatestring–ISO 3166-2 code, e.g. DE-BY
localestring–Language for classification text (headline/description); defaults to German
NameTypeReqDescription
countByClassobjectyesStation count per flood class name
sourceNoticesobjectyesDistinct notices of the listed gauges by key; a gauge names its own in sourceNoticeId
stationsarrayyes–
stationsWithFloodnumberyes–

No examples provided.

get_forecast ~152

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. Every result names the data provider in sourceNotice (search and flood situation: sourceNotices, keyed by sourceNoticeId); show that notice with any value, class or forecast you pass on, and the licence terms of the API require it.

NameTypeReqDescription
horizonHoursnumber–Hours ahead, default 72, capped at 240
stationIdstringyesNamespaced station id, e.g. "lhp:RP_2640010"
NameTypeReqDescription
countnumberyes–
generatedAt–yesModel run time; null when none was published
horizonHoursnumberyes–
notestringyes–
pointsarrayyes–
source–yes–
sourceNotice–yesNotice of the gauge as shown; show it with any value taken from this gauge. Null where none can be built, then no value is delivered
stationIdstringyes–
unitstringyes–
valueDivisornumberyesDivide valueCentimeters by this to read it in `unit`

No examples provided.

get_readings ~269

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. Every result names the data provider in sourceNotice (search and flood situation: sourceNotices, keyed by sourceNoticeId); show that notice with any value, class or forecast you pass on, and the licence terms of the API require it.

NameTypeReqDescription
fromstring–ISO 8601 start, e.g. 2026-06-01T00:00:00Z
stationIdstringyesNamespaced station id, e.g. "pegelonline:<uuid>" or "lhp:BY_10026301"
tostring–ISO 8601 end, defaults to now
typestring–Series type: level (default) or discharge (m³/s)
NameTypeReqDescription
countnumberyes–
dischargearray–Discharge series, m³/s
notestring–Present when the series was downsampled
readingsarray–Level series as stored valueCentimeters
sourceNotice–yesNotice of the gauge as shown; show it with any value taken from this gauge. Null where none can be built, then no value is delivered
stationIdstringyes–
summary–yesMin and max (level: in unit) and latest point; null when empty
unitstring–Unit of a level series; absent for discharge
valueDivisornumber–Divide valueCentimeters by this to read in unit

No examples provided.

get_station ~145

Master data of one station: measurement type, current value with its unit, thresholds (MNW/MHW, alert marks, as stored valueCentimeters), flood class, coordinates. Every result names the data provider in sourceNotice (search and flood situation: sourceNotices, keyed by sourceNoticeId); show that notice with any value, class or forecast you pass on, and the licence terms of the API require it.

NameTypeReqDescription
localestring–Language for classification text (headline/description); defaults to German
stationIdstringyesNamespaced station id, e.g. "pegelonline:<uuid>" or "lhp:BY_10026301"
NameTypeReqDescription
floodWarning–yesThe river section warning this gauge inherits; it describes the reach, not the gauge
idstringyes–
latestMeasuredAt–yes–
latestValue–yesLatest level, in `unit`
latestValueCentimeters–yes–
latitudenumberyes–
longitudenumberyes–
measurementTypestringyesriver | groundwater | sea_level | reservoir
namestringyes–
sourceNotice–yesNotice of the gauge as shown; show it with any value taken from this gauge. Null where none can be built, then no value is delivered
thresholdsarrayyes–
unitstringyes–
valueDivisornumberyesDivide any valueCentimeters by this to read it in `unit`
water–yes–
waterClassstringyesriver | lake | coast | groundwater — the group the gauge belongs to; measurementType says what it measures

No examples provided.

get_weather ~56

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

NameTypeReqDescription
stationIdstringyesNamespaced station id, e.g. "pegelonline:<uuid>" or "lhp:BY_10026301"
NameTypeReqDescription
attributionstringyes–
availablebooleanyesFalse when the forecast provider is unreachable
daily–yes–
stationIdstringyes–
stationNamestringyes–

No examples provided.

search_stations ~225

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. Every result names the data provider in sourceNotice (search and flood situation: sourceNotices, keyed by sourceNoticeId); show that notice with any value, class or forecast you pass on, and the licence terms of the API require it.

NameTypeReqDescription
federalStatestring–ISO 3166-2 code for a German state, e.g. DE-NW; CH, AT, CZ, LU or FR for a country
localestring–Language for classification text (headline/description); defaults to German
querystring–Station or water name, e.g. "Köln" or "Rhein"
waterClassarray–Only gauges of these classes: river, lake (lakes and reservoirs), coast (coast and tide), groundwater; omit for all
NameTypeReqDescription
notestring–Present when the result was capped
sourceNoticesobjectyesDistinct notices of the listed gauges by key; a gauge names its own in sourceNoticeId
stationsarrayyes–
totalMatchesnumberyesMatches before the result cap

No examples provided.

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.

remote · fluvigil.de

# add to Claude Code
claude mcp add --transport http de-fluvigil-pegel 'https://fluvigil.de/mcp'
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 90 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 974 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 6 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 de.fluvigil/pegel MCP server?

VerifyMCP ran 13 checks on de.fluvigil/pegel, 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.