# Basinwise (remote · basinwise.vercel.app)

Determines which NPDES stormwater permit governs a US site and its requirements, cited to source.

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

## Components

- remote · `basinwise.vercel.app`: 72/100 (this document), [markdown](https://verifymcp.io/servers/maxbeech-basinwise/api-mcp.md), [page](https://verifymcp.io/servers/maxbeech-basinwise/api-mcp)

## Channel facts

- Endpoint: `https://basinwise.vercel.app/api/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**: 80/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.
  - 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**: 57/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2115 tokens (~423/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - 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.
- **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 maxbeech-basinwise https://basinwise.vercel.app/api/mcp
```

### Codex

```toml
[mcp_servers.maxbeech-basinwise]
url = "https://basinwise.vercel.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "maxbeech-basinwise": {
      "type": "remote",
      "url": "https://basinwise.vercel.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add maxbeech-basinwise --url https://basinwise.vercel.app/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  maxbeech-basinwise:
    url: "https://basinwise.vercel.app/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "maxbeech-basinwise": {
      "type": "http",
      "url": "https://basinwise.vercel.app/api/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 72, +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 71, +4)

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

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-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 (5)

### `determine_permit` (~752 tokens)

Determine which stormwater permit governs a site

Determine which NPDES stormwater permit governs a construction or industrial site, and what that permit requires of it. Returns coverage ("required", "not_required" or "verify") with the reason, the governing permit and the version the answer was computed against, the jurisdiction and its permitting authority, the permit's eligibility screens, the requirements that attach to THIS site (each with the permit section it came from and a `because` explaining why it applies here rather than in general), the step-by-step derivation, and `notices`. ALWAYS surface `notices` verbatim to the user: it carries the preparer-credential warning, any coverage gap, and the fact that we do not perform the physical site inspections the permit requires. Deterministic, no model in the path. Requirements come back ONLY where we hold the governing permit's rules; where a state permit is identified but unread, `requirements` is empty and a notice says so rather than substituting the federal permit's numbers, so never treat an empty list as "nothing required". Free, no API key needed.

Input parameters:

- `acres` (number): Alias for disturbedAcres.
- `activity` (string, required): Required. Construction and industrial sites are governed by different permits and neither is assumed. "industrial" returns coverage "verify": EPA's Multi-Sector General Permit expired on 28 February…
- `aridClimate` (boolean): Arid, semi-arid or drought-stricken area, which may allow a reduced inspection frequency during the seasonally dry period.
- `dischargesToImpairedWater` (boolean): Discharges to a sediment or nutrient impaired water. OMIT IT if you do not know: it is never assumed false, and the determination reports the answer as unknown instead. It changes both the inspection…
- `dischargesToTier2Water` (boolean): Discharges to a Tier 2, 2.5 or 3 water. Same tri-state handling as dischargesToImpairedWater.
- `disturbedAcres` (number): TOTAL acres the project will disturb over its life. This is what the 1-acre coverage threshold is measured against. `acres` is accepted as an alias.
- `endDate` (string): ISO yyyy-mm-dd. Recorded on the determination.
- `federalFacility` (boolean): EPA's permit covers federal facilities in some delegated states.
- `maxDisturbedAcresAtOneTime` (number): Greatest acreage disturbed AT ANY ONE TIME. A different quantity from disturbedAcres, and the one the stabilisation deadline actually turns on (2022 CGP Table 2): a project over five acres in total s…
- `onTribalLand` (boolean): EPA retains NPDES authority in Indian country even inside a state that runs its own programme.
- `partOfLargerPlan` (boolean): Whether the project is part of a larger common plan of development or sale. Defaults to false. Send it explicitly: a half-acre lot inside a 40-acre subdivision IS covered, and this is the most common…
- `sectorCode` (string): MSGP industrial sector code. Industrial sites only.
- `startDate` (string): ISO yyyy-mm-dd. Recorded on the determination.
- `state` (string, required): Two-letter state, territory or DC code, e.g. "CA".

### `get_requirements` (~651 tokens)

Get the permit requirements for a site

The requirements for a site: inspection frequency, stabilisation deadlines, Notice of Intent and Notice of Termination deadlines, corrective-action windows, record retention and buffer rules, each citing the permit section it came from. Same engine and same parser as determine_permit, projected down. The coverage verdict, the eligibility screens and the notices come with it, because a requirement list detached from whether coverage is triggered at all is a half-answer. An empty `requirements` array with a notice means we have not read that jurisdiction's permit, NOT that nothing is required. Free, no API key needed.

Input parameters:

- `acres` (number): Alias for disturbedAcres.
- `activity` (string, required): Required. Construction and industrial sites are governed by different permits and neither is assumed. "industrial" returns coverage "verify": EPA's Multi-Sector General Permit expired on 28 February…
- `aridClimate` (boolean): Arid, semi-arid or drought-stricken area, which may allow a reduced inspection frequency during the seasonally dry period.
- `dischargesToImpairedWater` (boolean): Discharges to a sediment or nutrient impaired water. OMIT IT if you do not know: it is never assumed false, and the determination reports the answer as unknown instead. It changes both the inspection…
- `dischargesToTier2Water` (boolean): Discharges to a Tier 2, 2.5 or 3 water. Same tri-state handling as dischargesToImpairedWater.
- `disturbedAcres` (number): TOTAL acres the project will disturb over its life. This is what the 1-acre coverage threshold is measured against. `acres` is accepted as an alias.
- `endDate` (string): ISO yyyy-mm-dd. Recorded on the determination.
- `federalFacility` (boolean): EPA's permit covers federal facilities in some delegated states.
- `maxDisturbedAcresAtOneTime` (number): Greatest acreage disturbed AT ANY ONE TIME. A different quantity from disturbedAcres, and the one the stabilisation deadline actually turns on (2022 CGP Table 2): a project over five acres in total s…
- `onTribalLand` (boolean): EPA retains NPDES authority in Indian country even inside a state that runs its own programme.
- `partOfLargerPlan` (boolean): Whether the project is part of a larger common plan of development or sale. Defaults to false. Send it explicitly: a half-acre lot inside a 40-acre subdivision IS covered, and this is the most common…
- `sectorCode` (string): MSGP industrial sector code. Industrial sites only.
- `startDate` (string): ISO yyyy-mm-dd. Recorded on the determination.
- `state` (string, required): Two-letter state, territory or DC code, e.g. "CA".

### `get_credential_gate` (~240 tokens)

Does this state need a credentialed plan preparer?

Whether a state requires a credentialed preparer (California's Qualified SWPPP Developer, and the analogous credential elsewhere) to prepare or sign a stormwater pollution prevention plan, and whether that requirement bites for a site of this size. This is the answer that decides whether a generated document is the operator's deliverable or a DRAFT for a credentialed person to review and sign, so `documentStatus` states that consequence in plain language on every response. `gate` is "open", "gated", "conditional" or "unknown"; a state we have not verified returns "unknown" and must never be treated as open. `appliesToThisSite` is null when the trigger is an acreage threshold you did not give acres for, or a plan-scope test we cannot resolve from site facts. Free, no API key needed.

Input parameters:

- `acres` (number): Acres disturbed. Optional but worth sending: several states gate only above an acreage threshold, and without it a conditional state can only name the threshold rather than resolve it.
- `state` (string, required): Two-letter state, territory or DC code, e.g. "CA".

### `list_jurisdictions` (~115 tokens)

List every jurisdiction and its permitting authority

Every state, territory and DC we hold a row for: NPDES authorisation status, the governing permit and its number, the agency name and URL, and the preparer-credential gate. Jurisdictions we have NOT verified are listed with confidence "unverified" and a note naming the agency to confirm with, rather than being omitted, because a jurisdiction missing from a coverage list reads as "no permit applies" and that is never what it means. Takes no arguments. Free, no API key needed.

### `get_usage` (~95 tokens)

What this key is allowed to do

What the credential on this connection is allowed to do: the tier it resolves to (anonymous, sandbox, test key, or a live key on a plan), the per-minute burst, the daily or monthly allowance, and whether calls bill. Call it once at the start of a long task to pace yourself, rather than discovering the ceiling as a rate_limited error halfway through. Takes no arguments. Free, no API key needed.

## Diagnostics

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

## Score history

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

## Links

- Remote endpoint: https://basinwise.vercel.app/api/mcp
- Website: https://basinwise.vercel.app/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/maxbeech-basinwise/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/maxbeech-basinwise/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/maxbeech-basinwise/api-mcp