Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Property Hazard MCP

REMOTE · MCP.ZIPQUOTE.AI

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

Available components

0 this week 83 Trust /100

Last scanned (22 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 → Why this is hard to 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability74
  • 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 28 Sept 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
  • 25 Sept 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 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 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
Diagnostics

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 21 Nov 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 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA384 641e6dbca65f745bc5ff2fd421f7d3eced9
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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.zipquote.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
zipquote.ai. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

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
MCP tools · 1 exposed · ~97 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
assess_property_hazard ~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.

NameTypeReqDescription
addressstringyes–
NameTypeReqDescription
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_addressstringyesThe 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
validatedbooleanyesWhether the address was successfully validated/geocoded
wildfire_score––Coarse wildfire hazard tier, 0 (none) to 4 (very high)

No examples provided.

Install

How do I install the Property Hazard MCP server?

Property Hazard MCP is a hosted endpoint at https://mcp.zipquote.ai/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.

remote · mcp.zipquote.ai

# add to Claude Code
claude mcp add --transport http ai-zipquote-us-property-hazard-risk 'https://mcp.zipquote.ai/mcp'
Common questions

What is the Property Hazard MCP server?

Property Hazard MCP is listed in the public MCP registry as ai.zipquote/us-property-hazard-risk. Flood, wildfire, earthquake, and coastal-storm hazard lookup for a US property. This page covers its hosted endpoint (https://mcp.zipquote.ai/mcp).

Is the Property Hazard MCP server safe to use?

Property Hazard MCP scores 83 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 Property Hazard MCP server expose?

Property Hazard MCP exposes 1 tool: assess_property_hazard. Their descriptions and schemas cost roughly 97 tokens of context every time the server is loaded.

Does the Property Hazard MCP server require authentication?

No. We connected to Property Hazard MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Property Hazard MCP server still maintained?

Property Hazard MCP is still listed as active in the MCP registry. We last reached this channel on 21 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 Property Hazard MCP server?

VerifyMCP ran 13 checks on Property Hazard MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.