# com.mamoie/hazard (remote · mamoie.com)

Disaster risk for any Japanese address from official government data. 6 hazards, sources cited.

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

## Components

- remote · `mamoie.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-mamoie-hazard/api-mcp.md), [page](https://verifymcp.io/servers/com-mamoie-hazard/api-mcp)

## Channel facts

- Endpoint: `https://mamoie.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 277 tokens (~277/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-mamoie-hazard https://mamoie.com/api/mcp
```

### Codex

```toml
[mcp_servers.com-mamoie-hazard]
url = "https://mamoie.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mamoie-hazard": {
      "type": "remote",
      "url": "https://mamoie.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mamoie-hazard --url https://mamoie.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mamoie-hazard:
    url: "https://mamoie.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-mamoie-hazard": {
      "type": "http",
      "url": "https://mamoie.com/api/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-08-03 (score 68, +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.

### 2026-07-31 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +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-07-27 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (1)

### `check_home_disaster_risk` (~217 tokens)

日本の住所の災害リスク（洪水・地震・土砂・津波・高潮・液状化）を、国の公式データ（重ねるハザードマップ・J-SHIS）に基づいて判定して返します。日本国内の住所または緯度経度に対応。出典つき。

Input parameters:

- `address` (string, required): 日本の住所（例: 東京都墨田区押上1-1-2）。緯度経度で指定する場合は lat/lon を使う。
- `lang` (string): 応答の言語。'en' で英語サマリー（国外投資家向け）。既定は 'ja'。
- `lat` (number): 緯度（address の代わりに座標で指定する場合）
- `lon` (number): 経度（address の代わりに座標で指定する場合）

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mamoie-hazard/api-mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 67
- 2026-07-30: 66
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 64
- 2026-07-26: 63

## Links

- Remote endpoint: https://mamoie.com/api/mcp
- Website: https://mamoie.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-mamoie-hazard/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mamoie-hazard/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-mamoie-hazard/api-mcp