# Trinkwassermonitor (remote · trinkwassermonitor.ink)

Geprüfte Trinkwasserwerte deutscher Städte mit Quelle, Messdatum und Grenzwert (TrinkwV)

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `trinkwassermonitor.ink`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ink-trinkwassermonitor-trinkwasser/api-v1-mcp.md), [page](https://verifymcp.io/servers/ink-trinkwassermonitor-trinkwasser/api-v1-mcp)

## Channel facts

- Endpoint: `https://trinkwassermonitor.ink/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.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-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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**: 74/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http ink-trinkwassermonitor-trinkwasser 'https://trinkwassermonitor.ink/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ink-trinkwassermonitor-trinkwasser": {
      "url": "https://trinkwassermonitor.ink/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ink-trinkwassermonitor-trinkwasser": {
      "type": "http",
      "url": "https://trinkwassermonitor.ink/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ink-trinkwassermonitor-trinkwasser]
url = "https://trinkwassermonitor.ink/api/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ink-trinkwassermonitor-trinkwasser": {
      "type": "remote",
      "url": "https://trinkwassermonitor.ink/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ink-trinkwassermonitor-trinkwasser --url 'https://trinkwassermonitor.ink/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ink-trinkwassermonitor-trinkwasser:
    url: "https://trinkwassermonitor.ink/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ink-trinkwassermonitor-trinkwasser": {
      "Transport": "http",
      "Url": "https://trinkwassermonitor.ink/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ink-trinkwassermonitor-trinkwasser -t streamable-http -u 'https://trinkwassermonitor.ink/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ink-trinkwassermonitor-trinkwasser": {
      "type": "http",
      "url": "https://trinkwassermonitor.ink/api/v1/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-11-04 (score 75, +1)

- [security] 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
- [functional regression] Schema quality: pass → fail

### 2026-11-02 (score 74, +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.

### 2026-10-31 (score 73, +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.

### 2026-10-29 (score 72, +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.

### 2026-10-27 (score 71, +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.

### 2026-10-24 (score 70, +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.

### 2026-10-22 (score 69, +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.

### 2026-10-20 (score 68, +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.

## MCP tools (7)

### `find_city` (~67 tokens)

Ort finden

Sucht Orte mit ausgewertetem Prüfbericht nach Name oder fünfstelliger Postleitzahl. Liefert slug, Name und PLZ für die anderen Tools.

Input parameters:

- `query` (string, required): Ortsname oder PLZ, z. B. "Würzburg" oder "97070"

### `get_water_quality` (~128 tokens)

Trinkwasserwerte eines Ortes

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.

Input parameters:

- `city` (string, required): slug, Ortsname oder PLZ
- `substance` (string): optional: Stoffschlüssel, z. B. nitrat, pfas, haerte, blei, uran, natrium

### `verify_claim` (~109 tokens)

Aussage gegenprüfen

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.

Input parameters:

- `city` (string, required): slug, Ortsname oder PLZ
- `substance` (string, required): Stoffschlüssel, z. B. nitrat
- `unit` (string): optional: mg/l, µg/l, ng/l oder °dH
- `value` (number, required): behaupteter Wert

### `compare_cities` (~115 tokens)

Orte vergleichen

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

Input parameters:

- `cities` (array, required): slugs, Ortsnamen oder PLZ
- `substance` (string): optional: nur dieser Stoffschlüssel

### `get_data_gaps` (~116 tokens)

Datenlücken je Stoff

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.

Input parameters:

- `state` (string): optional: Bundesland-Slug, z. B. baden-wuerttemberg, bayern, berlin
- `substance` (string): optional: Stoffschlüssel, z. B. pfas; ohne Angabe die Kernstoffe

### `get_changes` (~77 tokens)

Änderungen zwischen Prüfberichten

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.

Input parameters:

- `city` (string): optional: slug, Ortsname oder PLZ

### `get_legal_limits` (~50 tokens)

Grenzwerte der Trinkwasserverordnung

Die heute geltenden Grenzwerte der deutschen Trinkwasserverordnung (TrinkwV 2023) mit Einheit, Art (Grenzwert oder Indikatorparameter) und Fundstelle.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ink-trinkwassermonitor-trinkwasser/api-v1-mcp#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 71
- 2026-10-27: 71
- 2026-10-26: 70
- 2026-10-25: 70
- 2026-10-24: 70
- 2026-10-23: 69
- 2026-10-22: 69
- 2026-10-21: 68
- 2026-10-20: 68
- 2026-10-19: 67
- 2026-10-18: 67

## Common questions

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

### What did VerifyMCP test on the Trinkwassermonitor MCP server?

VerifyMCP ran 12 checks on Trinkwassermonitor, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Trinkwassermonitor: Authorization. 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.

## Links

- Remote endpoint: https://trinkwassermonitor.ink/api/v1/mcp
- Website: https://trinkwassermonitor.ink/downloads/#mcp
- Changelog RSS feed: https://verifymcp.io/servers/ink-trinkwassermonitor-trinkwasser/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ink-trinkwassermonitor-trinkwasser/api-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ink-trinkwassermonitor-trinkwasser/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ink-trinkwassermonitor-trinkwasser/api-v1-mcp