# io.github.squidcode/tapwatermap (remote · mcp.tapwatermap.com)

Query US tap-water quality from the EPA's SDWIS records — by city, system, or contaminant.

- Trust score: 71/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.tapwatermap.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/squidcode-tapwatermap/mcp.md), [page](https://verifymcp.io/servers/squidcode-tapwatermap/mcp)

## Channel facts

- Endpoint: `https://mcp.tapwatermap.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 694 tokens (~69/item across 10 items; 10 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**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 59% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http squidcode-tapwatermap https://mcp.tapwatermap.com/mcp
```

### Codex

```toml
[mcp_servers.squidcode-tapwatermap]
url = "https://mcp.tapwatermap.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "squidcode-tapwatermap": {
      "type": "remote",
      "url": "https://mcp.tapwatermap.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add squidcode-tapwatermap --url https://mcp.tapwatermap.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  squidcode-tapwatermap:
    url: "https://mcp.tapwatermap.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "squidcode-tapwatermap": {
      "type": "http",
      "url": "https://mcp.tapwatermap.com/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-08-02 (score 71, +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-07-31 (score 70, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 66, +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.

### 2026-07-27 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (10)

### `search` (~59 tokens)

Search TapWaterMap for US cities by name. Returns matching cities with an id you can pass to `fetch`. (ChatGPT/Deep-Research compatible.)

Input parameters:

- `query` (string, required): City name or partial name, e.g. 'Burlington'.

### `fetch` (~64 tokens)

Fetch the full plain-English EPA tap-water record for a city id (e.g. 'vt/burlington') returned by `search`. (ChatGPT/Deep-Research compatible.)

Input parameters:

- `id` (string, required): City id like 'vt/burlington' (state/slug).

### `search_cities` (~63 tokens)

Find covered US cities by name, optionally within a state. Returns counts + the page URL for each.

Input parameters:

- `limit` (integer)
- `query` (string, required)
- `state` (string): Optional 2-letter state code, e.g. 'TX'.

### `get_city_water` (~94 tokens)

The core tool: what the EPA has on record for a city's tap water — the active community water systems serving it, populations, sources, and violations (contaminant, health-based or not, dates, status, level vs limit when recorded). Plain-English, sourced, never a safety verdict.

Input parameters:

- `city` (string, required)
- `state` (string, required): 2-letter state code, e.g. 'VT'.

### `get_water_system` (~50 tokens)

EPA record for a single water system by its PWSID (e.g. 'VT0005053'): name, population served, source, and violations.

Input parameters:

- `pwsid` (string, required)

### `list_state_cities` (~34 tokens)

List all covered cities in a state (with violation counts).

Input parameters:

- `state` (string, required): 2-letter state code.

### `find_cities` (~121 tokens)

Filter/rank cities across the dataset — e.g. cities in TX with open health-based violations, or cities with a specific contaminant. Returns ranked matches.

Input parameters:

- `contaminant` (string): Optional EPA contaminant code or name (use explain_contaminant to find a code).
- `healthBasedOnly` (boolean)
- `limit` (integer)
- `minPopulation` (integer)
- `openViolationsOnly` (boolean): Only cities with violations not returned to compliance.
- `state` (string): Optional 2-letter state code.

### `compare_cities` (~51 tokens)

Compare the EPA records of several cities side by side. Pass cities as 'City, ST' strings.

Input parameters:

- `cities` (array, required): e.g. ['Burlington, VT', 'Houston, TX']

### `explain_contaminant` (~78 tokens)

Plain-English explanation of an EPA contaminant by name or code: the EPA name, whether the EPA classifies it as health-based, and how often it appears in our records. Not medical advice.

Input parameters:

- `contaminant` (string, required): Contaminant name or EPA code, e.g. 'TTHM' or '2950'.

### `coverage_stats` (~29 tokens)

What TapWaterMap covers: states, cities, total EPA violation records, and the data quarter/date.

## Diagnostics

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

## Score history

- 2026-08-03: 71
- 2026-08-02: 71
- 2026-08-01: 70
- 2026-07-31: 70
- 2026-07-30: 67
- 2026-07-29: 66
- 2026-07-28: 66
- 2026-07-27: 65
- 2026-07-26: 64

## Links

- Remote endpoint: https://mcp.tapwatermap.com/mcp
- Website: https://tapwatermap.com/developers/
- Changelog RSS feed: https://verifymcp.io/servers/squidcode-tapwatermap/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/squidcode-tapwatermap/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/squidcode-tapwatermap/mcp