location-risk-mcp
Related Servers
Alternatives to location-risk-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceProvides per-property multi-peril risk scores (flood, wildfire, wind, hail, crime, etc.) for an address, returning A-F grades and 0-100 scores across 25+ hazard types for insurance underwriting and due diligence.83 npmMIT- FlicenseNot gradedqualityDmaintenanceProperty intelligence API for US real estate. Returns 16+ data points for any US address: noise levels, wetlands, slope, natural light, powerline proximity, crime rates, property facing direction, zoning, public record, radon risk, natural hazards (earthquake, flood, wildfire), neighborhood demographics, falling tree risk, RF/cell tower exposure, and nearby school.-
- AlicenseNot gradedqualityDmaintenanceAssesses natural hazard exposure (flood, wildfire, earthquake, coastal proximity) for a single US property address using only free, keyless public data.MIT
- AlicenseAqualityCmaintenanceInstant U.S. property intelligence for AI agents. Zoning, Buildability™ Score, ADU eligibility, flood risk, and more from 20+ government sources. Pay-as-you-go: $5 per analysis (prepaid credits). Free Score available at buildability.us. Get a key at buildability.us/api.51MIT
- AlicenseNot gradedqualityCmaintenanceEnables US address verification and standardization, validating deliverability and returning USPS-standardized data, plus property enrichment with 350+ tax assessor and deed attributes for a given address.282 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run pre-sign risk checks on transactions, approvals, EIP-712 signatures, token addresses, wallet approvals, sanctions screening, and prompt-injection texts, returning green/orange/red verdicts with machine-readable reason codes before signing.1AGPL 3.0
TDQS
Scored across 3 tools
The three tools form a strict sequential pipeline (standardise → enrich → summarise) and each targets a distinct stage with clearly different outputs: a location_id, hazard blocks, and a decision-support summary. Descriptions explicitly state the handoff (e.g. 'use location.location_id next', 'calls enrich_location itself if needed'), so there is no realistic misselection.
All three names follow the same verb_noun convention (standardise_address, enrich_location, summarise_risk_context) with consistent British spelling and snake_case. The pattern is fully predictable and readable.
Three tools is on the lean side, but each is a substantial, broad operation covering many sub-capabilities (geocoding, hazards, summarisation), so nothing feels redundant or missing. A single-address-at-a-time surface is a reasonable scope, though one extra tool (e.g. batch or lookup-by-id) could round it out.
The full lifecycle from free-text address to risk pre-screen is covered end-to-end, including ambiguity handling, gap reporting, and an internal enrich call. Minor gaps exist: no batch/multi-address processing, no standalone retrieval of a stored location or risk record by location_id, and no way to inspect available data sources or coverage beyond per-result gaps.