# Property Risk Check (remote · public-domain-check-production.up.railway.app)

One-call US property hazard report: flood, seismic, 18 FEMA hazard ratings, disasters. x402.

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `public-domain-check-production.up.railway.app`: 79/100 (this document), [markdown](https://verifymcp.io/servers/chomkaevan-property-risk/property-mcp.md), [page](https://verifymcp.io/servers/chomkaevan-property-risk/property-mcp)

## Channel facts

- Endpoint: `https://public-domain-check-production.up.railway.app/property/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-11-21.

- **Endpoint Security**: 91/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation.
  - 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**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 140 tokens (~140/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Property Risk Check MCP server?

Property Risk Check is a hosted endpoint at https://public-domain-check-production.up.railway.app/property/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.

### Claude

```bash
claude mcp add --transport http chomkaevan-property-risk 'https://public-domain-check-production.up.railway.app/property/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "chomkaevan-property-risk": {
      "url": "https://public-domain-check-production.up.railway.app/property/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "chomkaevan-property-risk": {
      "type": "http",
      "url": "https://public-domain-check-production.up.railway.app/property/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.chomkaevan-property-risk]
url = "https://public-domain-check-production.up.railway.app/property/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chomkaevan-property-risk": {
      "type": "remote",
      "url": "https://public-domain-check-production.up.railway.app/property/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chomkaevan-property-risk --url 'https://public-domain-check-production.up.railway.app/property/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chomkaevan-property-risk:
    url: "https://public-domain-check-production.up.railway.app/property/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "chomkaevan-property-risk": {
      "Transport": "http",
      "Url": "https://public-domain-check-production.up.railway.app/property/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add chomkaevan-property-risk -t streamable-http -u 'https://public-domain-check-production.up.railway.app/property/mcp'
```

### Other

```json
{
  "mcpServers": {
    "chomkaevan-property-risk": {
      "type": "http",
      "url": "https://public-domain-check-production.up.railway.app/property/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-11-21 (score 79, +1)

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

### 2026-11-19 (score 78, +1)

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

### 2026-11-17 (score 77, +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-11-15 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 75)

First indexed and scored.

## MCP tools (1)

### `check_property_risk` (~140 tokens)

FEMA flood zone and seismic risk for a US address

One-call natural hazard report for a US address or coordinates: overall risk and its drivers, FEMA flood zone and flood-insurance requirement, ratings for wildfire, hurricane, tornado, heat, flooding, earthquake and more, and the county's disaster history. Use when evaluating, listing, insuring or financing a property, or when asked about flood zones or natural hazard risk at an address. Not charged if the address can't be found. Costs $0.02 (x402, USDC on Base).

Input parameters:

- `address` (string): US street address with city and state or ZIP
- `lat` (number)
- `lon` (number)

## Diagnostics

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

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75

## Common questions

### What is the Property Risk Check MCP server?

Property Risk Check is an MCP server listed in the public MCP registry as io.github.chomkaevan/property-risk. One-call US property hazard report: flood, seismic, 18 FEMA hazard ratings, disasters. x402. This page covers its hosted endpoint (https://public-domain-check-production.up.railway.app/property/mcp).

### Is the Property Risk Check MCP server safe to use?

Property Risk Check scores 79 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 Risk Check MCP server expose?

Property Risk Check exposes 1 tool: check_property_risk. Their descriptions and schemas cost roughly 140 tokens of context every time the server is loaded.

### Does the Property Risk Check MCP server require authentication?

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

### Is the Property Risk Check MCP server still maintained?

Property Risk Check 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 Risk Check MCP server?

VerifyMCP ran 13 checks on Property Risk Check, 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.

## Links

- Remote endpoint: https://public-domain-check-production.up.railway.app/property/mcp
- Repository: https://github.com/chomkaevan/public-domain-check-mcp
- Website: https://public-domain-check-production.up.railway.app/property
- Changelog RSS feed: https://verifymcp.io/servers/chomkaevan-property-risk/property-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/chomkaevan-property-risk/property-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/chomkaevan-property-risk/property-mcp.json
- HTML version of this page: https://verifymcp.io/servers/chomkaevan-property-risk/property-mcp
