assess_property_hazard — Property Hazard MCP MCP Tool
assess_property_hazard
(assess property hazard) is one of 1 tool on the
Property Hazard MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call assess_property_hazard from your client
- Claude Code Property Hazard MCP assess_property_hazard run in your project directory
- Claude Desktop Property Hazard MCP assess_property_hazard ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Property Hazard MCP assess_property_hazard ~/.cursor/mcp.json
- VS Code Property Hazard MCP assess_property_hazard .vscode/mcp.json
- Zed Property Hazard MCP assess_property_hazard ~/.config/zed/settings.json
- Windsurf Property Hazard MCP assess_property_hazard ~/.codeium/windsurf/mcp_config.json
- Cline Property Hazard MCP assess_property_hazard ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Property Hazard MCP assess_property_hazard ~/.gemini/settings.json
- Grok Property Hazard MCP assess_property_hazard .mcp.json (in your project root)
- ChatGPT Property Hazard MCP assess_property_hazard Settings → Connectors → Advanced → Developer mode
- Claude.ai Property Hazard MCP assess_property_hazard Settings → Connectors → Add custom connector
- LangChain Property Hazard MCP assess_property_hazard pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http us-property-hazard-risk https://mcp.zipquote.ai/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.