Trinkwassermonitor
REMOTE · TRINKWASSERMONITOR.INK
Geprüfte Trinkwasserwerte deutscher Städte mit Quelle, Messdatum und Grenzwert (TrinkwV)
Available components
Last scanned (14 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 840 tokens (~120/item across 7 items; 7 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 Management60
- Stability observed for 18 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compare_cities” rewrote its description, which is the text the model reads security
- Tool “get_changes” rewrote its description, which is the text the model reads security
- Tool “get_water_quality” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://trinkwassermonitor.ink/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trinkwassermonitor.ink | CN=YE2,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5892ae852146c9a166d76802e7d471c74d9 |
| SANs: *.trinkwassermonitor.ink, trinkwassermonitor.ink | ||||||
| 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 trinkwassermonitor.ink. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ink. | present | 19420 | 13 | Verified |
| trinkwassermonitor.ink. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trinkwassermonitor.ink/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://trinkwassermonitor.ink/api/v1/mcp | HTTPS enforced | 301 | https://trinkwassermonitor.ink/api/v1/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_cities Orte vergleichen ~115
Stellt die Werte des neuesten Prüfberichts von 2 bis 5 Orten nebeneinander (Hauptversorgung, je Stoff mit Messdatum, Grenzwert und Quelle). Fehlt ein Stoff, steht not_reported; dieses Werkzeug bildet keine Rangfolge und keine Gesamtnote (der WaterScore steht nur auf den Stadtseiten, immer mit Angabe der Datenabdeckung).
| Name | Type | Req | Description |
|---|---|---|---|
| cities | array | yes | slugs, Ortsnamen oder PLZ |
| substance | string | – | optional: nur dieser Stoffschlüssel |
No output schema declared.
No examples provided.
find_city Ort finden ~67
Sucht Orte mit ausgewertetem Prüfbericht nach Name oder fünfstelliger Postleitzahl. Liefert slug, Name und PLZ für die anderen Tools.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Ortsname oder PLZ, z. B. "Würzburg" oder "97070" |
No output schema declared.
No examples provided.
get_changes Änderungen zwischen Prüfberichten ~77
Werte, die in zwei aufeinanderfolgenden Prüfberichten desselben Wassers stehen: vorher, nachher, beide Quellen (mit SHA-256, soweit die Berichte als Datei vorliegen). Ohne Ursachenangabe, solange der Versorger keine nennt.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | optional: slug, Ortsname oder PLZ |
No output schema declared.
No examples provided.
get_data_gaps Datenlücken je Stoff ~116
Wie viele der ausgewerteten Orte (Deutschland oder ein Bundesland) für einen Stoff einen Wert im Prüfbericht nennen und wie viele nicht – mit fertigem Zitiersatz. Zählt nur ausgewertete Orte, nicht alle Versorgungsgebiete.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | optional: Bundesland-Slug, z. B. baden-wuerttemberg, bayern, berlin |
| substance | string | – | optional: Stoffschlüssel, z. B. pfas; ohne Angabe die Kernstoffe |
No output schema declared.
No examples provided.
get_legal_limits Grenzwerte der Trinkwasserverordnung ~50
Die heute geltenden Grenzwerte der deutschen Trinkwasserverordnung (TrinkwV 2023) mit Einheit, Art (Grenzwert oder Indikatorparameter) und Fundstelle.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_water_quality Trinkwasserwerte eines Ortes ~128
Alle Werte des neuesten Prüfberichts eines Ortes (je Versorgungszone) als Beleg-Objekte: Wert oder Status (measured, below_detection, not_reported), Einheit, Messdatum, Grenzwert mit Rechtsgrundlage, Quelle (mit SHA-256, soweit der Bericht als Datei vorliegt), fertiger Zitiersatz.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | slug, Ortsname oder PLZ |
| substance | string | – | optional: Stoffschlüssel, z. B. nitrat, pfas, haerte, blei, uran, natrium |
No output schema declared.
No examples provided.
verify_claim Aussage gegenprüfen ~109
Prüft eine Aussage wie "Nitrat in Würzburg 37,3 mg/l" gegen den neuesten Prüfbericht: supported, contradicted, outdated oder no_data, mit Beleg.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | slug, Ortsname oder PLZ |
| substance | string | yes | Stoffschlüssel, z. B. nitrat |
| unit | string | – | optional: mg/l, µg/l, ng/l oder °dH |
| value | number | yes | behaupteter Wert |
No output schema declared.
No examples provided.
How do I install the Trinkwassermonitor MCP server?
Trinkwassermonitor is a hosted endpoint at https://trinkwassermonitor.ink/api/v1/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 · trinkwassermonitor.ink
claude mcp add --transport http ink-trinkwassermonitor-trinkwasser 'https://trinkwassermonitor.ink/api/v1/mcp'
What is the Trinkwassermonitor MCP server?
Trinkwassermonitor is an MCP server listed in the public MCP registry as ink.trinkwassermonitor/trinkwasser. Geprüfte Trinkwasserwerte deutscher Städte mit Quelle, Messdatum und Grenzwert (TrinkwV). This page covers its hosted endpoint (https://trinkwassermonitor.ink/api/v1/mcp).
Is the Trinkwassermonitor MCP server safe to use?
Trinkwassermonitor scores 75 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 Trinkwassermonitor MCP server expose?
Trinkwassermonitor exposes 7 tools: find_city, get_water_quality, verify_claim, compare_cities, get_data_gaps, and 2 more. Their descriptions and schemas cost roughly 662 tokens of context every time the server is loaded.
Does the Trinkwassermonitor MCP server require authentication?
No. We connected to Trinkwassermonitor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Trinkwassermonitor MCP server still maintained?
Trinkwassermonitor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.