# Property Hazard MCP (remote · mcp.zipquote.ai)

Flood, wildfire, earthquake, and coastal-storm hazard lookup for a US property.

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

## Components

- remote · `mcp.zipquote.ai`: 69/100 (this document), [markdown](https://verifymcp.io/servers/ai-zipquote-us-property-hazard-risk/mcp.md), [page](https://verifymcp.io/servers/ai-zipquote-us-property-hazard-risk/mcp)

## Channel facts

- Endpoint: `https://mcp.zipquote.ai/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**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 145 tokens (~145/item across 1 items; 1 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**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 ai-zipquote-us-property-hazard-risk https://mcp.zipquote.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-zipquote-us-property-hazard-risk]
url = "https://mcp.zipquote.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-zipquote-us-property-hazard-risk": {
      "type": "remote",
      "url": "https://mcp.zipquote.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-zipquote-us-property-hazard-risk --url https://mcp.zipquote.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-zipquote-us-property-hazard-risk:
    url: "https://mcp.zipquote.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-zipquote-us-property-hazard-risk": {
      "type": "http",
      "url": "https://mcp.zipquote.ai/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-03 (score 69, +1)

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

### 2026-08-01 (score 68, +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-07-31 (score 67, +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 63, 0)

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

### 2026-07-29 (score 63, +1)

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

### 2026-07-28 (score 62, +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 61, 0)

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

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

First indexed and scored.

## MCP tools (1)

### `assess_property_hazard` (~97 tokens)

Assess Property Hazard Risk

Assess natural hazard exposure for a single US property address.

    Validates and geocodes the address (US Census Bureau geocoder), then looks
    up FEMA flood zone, wildfire hazard, USGS seismic PGA, active fault
    proximity, and coastal proximity. Returns a location-only hazard score
    (0-100) and tier. US addresses only; no building characteristics required.

Input parameters:

- `address` (string, required)

Output parameters:

- `coastal_distance_miles`: Distance to the nearest coastline, in miles
- `fault_distance_miles`: Distance to the nearest known active fault, in miles
- `flood_available`: Whether the FEMA flood zone lookup succeeded
- `flood_zone`: FEMA flood zone code (e.g. AE, X, VE); null if unavailable
- `hazard_drivers`: Up to 5 human-readable factors driving the score
- `hazard_score`: Deterministic location-only hazard score, 0-100
- `hazard_tier`: Hazard tier label: Low, Moderate, High, or Very High
- `input_address` (string): The address as provided by the caller
- `lat`: Latitude of the matched address
- `lng`: Longitude of the matched address
- `matched_address`: Normalized address returned by the geocoder
- `message`: Explanation of why validation failed, if it did
- `seismic_pga`: USGS peak ground acceleration in g (ASCE 7-22)
- `sfha`: Whether the address is in a Special Flood Hazard Area
- `validated` (boolean): Whether the address was successfully validated/geocoded
- `wildfire_score`: Coarse wildfire hazard tier, 0 (none) to 4 (very high)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-zipquote-us-property-hazard-risk/mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 68
- 2026-07-31: 67
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 61

## Links

- Remote endpoint: https://mcp.zipquote.ai/mcp
- Repository: https://github.com/ericshenus/us-property-hazard-risk
- Changelog RSS feed: https://verifymcp.io/servers/ai-zipquote-us-property-hazard-risk/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-zipquote-us-property-hazard-risk/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-zipquote-us-property-hazard-risk/mcp