Property Hazard MCP
REMOTE · MCP.ZIPQUOTE.AI · SCANNED AUG 3
Flood, wildfire, earthquake, and coastal-storm hazard lookup for a US property.
Available components
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 →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 145 tokens (~145/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.zipquote.ai
claude mcp add --transport http ai-zipquote-us-property-hazard-risk https://mcp.zipquote.ai/mcp
[mcp_servers.ai-zipquote-us-property-hazard-risk] url = "https://mcp.zipquote.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-zipquote-us-property-hazard-risk": {
"type": "remote",
"url": "https://mcp.zipquote.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-zipquote-us-property-hazard-risk --url https://mcp.zipquote.ai/mcp --transport streamable-http
mcp_servers:
ai-zipquote-us-property-hazard-risk:
url: "https://mcp.zipquote.ai/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 1 Aug 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.
- 31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
First indexed and scored.
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 3 Aug 2026 · Probed https://mcp.zipquote.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zipquote.ai | CN=YE2,O=Let's Encrypt,C=US | 11 Jul 2026 | 9 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5195b648de53d678845f0aa4192ab8730cc |
| SANs: *.zipquote.ai, zipquote.ai | ||||||
| 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 |
DNSSEC insecure
Validation of mcp.zipquote.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| zipquote.ai. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zipquote.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.zipquote.ai/mcp | HTTPS enforced | 308 | https://mcp.zipquote.ai/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.
assess_property_hazard Assess Property Hazard Risk ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Whether the address was successfully validated/geocoded |
| wildfire_score | — | — | Coarse wildfire hazard tier, 0 (none) to 4 (very high) |
No examples provided.