nankai-trough-mcp

# nankai-trough-mcp

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)

**An honest Nankai Trough (南海トラフ地震) earthquake hazard + building-safety engine for AI assistants.** Ask "how bad is the Nankai Trough quake, how far does it reach, and what does that mean for a house built in 1978?" — and get official Japanese government figures, every one cited and dated, with a route to the official maps for your exact address. It never tells you you're "safe."

It reports what 内閣府 (Cabinet Office), 地震本部, 気象庁, and 国土交通省 actually publish — and where a figure isn't verifiable, it points you at the source instead of inventing one. Bilingual EN/JA. Runs locally, no API keys.

> **⚠️ Not a prediction, not a verdict.** This explains official data and routes you to official guidance and a professional seismic diagnosis (耐震診断). Always confirm with your municipality and official hazard maps. In an emergency, follow official evacuation instructions.

## Why it exists

Most people underestimate the *reach*. The 30-year probability was revised by 地震本部 in **September 2025** away from the old single "80%" to a two-model range — **60–90%+ (higher model) / 20–50%** — intensity-7 shaking is projected across **10 prefectures**, and **764 municipalities in 31 prefectures** face major shaking or a 3 m+ tsunami. "I'm inland, so I'm fine" is exactly the assumption this corrects.

The authoritative data is real, but it's scattered across five agencies and mostly buried in PDFs. This server makes it honest, cited, and usable from an AI assistant — without ever inventing a number.

## The honesty contract

- **No verdicts.** It reports official figures + plain-language meaning, never "your home is safe/unsafe."
- **Every figure cites its official source + date.** If a value isn't verifiable in a primary source, it points to the source instead of guessing.
- **Probabilistic ≠ scenario.** J-SHIS (all-source probability) is never presented as the Nankai scenario (Cabinet Office).
- **Building safety can't be looked up** — it's classified from the build year + structure *you* provide. No fabricated per-building data.

## Install

```bash
claude mcp add nankai -- npx -y nankai-trough-mcp
```

### JSON config

The server config is the same across clients; only the file path differs.

<details>
<summary>Claude Code — <code>~/.claude/.mcp.json</code></summary>

```json
{
  "mcpServers": {
    "nankai": { "command": "npx", "args": ["-y", "nankai-trough-mcp"] }
  }
}
```

</details>

<details>
<summary>Cursor — <code>~/.cursor/mcp.json</code></summary>

```json
{
  "mcpServers": {
    "nankai": { "command": "npx", "args": ["-y", "nankai-trough-mcp"] }
  }
}
```

</details>

<details>
<summary>VS Code (GitHub Copilot) — <code>.vscode/mcp.json</code></summary>

```json
{
  "servers": {
    "nankai": { "type": "stdio", "command": "npx", "args": ["-y", "nankai-trough-mcp"] }
  }
}
```

</details>

<details>
<summary>Claude Desktop — <code>claude_desktop_config.json</code></summary>

```json
{
  "mcpServers": {
    "nankai": { "command": "npx", "args": ["-y", "nankai-trough-mcp"] }
  }
}
```

Config path:
- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`

</details>

### From source

```bash
git clone https://github.com/mrslbt/nankai-trough-mcp.git
cd nankai-trough-mcp
npm install && npm run build
```

Point the client config at the built entry:

```json
{ "command": "node", "args": ["/absolute/path/to/nankai-trough-mcp/dist/index.js"] }
```

## Tools

| Tool | Description |
|---|---|
| `nankai_overview` | The official 2025 scenario's scale and reach — probability, casualties, intensity-7 reach, tsunami — each with its source. Start here. |
| `official_hazard_maps` | Address → links to the **official** per-address hazard maps, where the exact predicted intensity and tsunami live. This server bridges; it doesn't invent those numbers. |
| `building_seismic_check` | Build year + structure → 旧耐震 / 新耐震 / 2000-standard classification with honest context. Not a verdict. |
| `taishin_subsidy_guide` | Routes to subsidised, often-free 耐震診断 / 耐震補強 programs and the national support framework. |
| `shindo_meaning` | What a JMA intensity (震度 5弱–7) means for people and buildings, on the official 気象庁 scale. |
| `geocode_address` | Address → coordinates via the GSI geocoder. Utility. |

Prompts: `assess_home_earthquake_risk`, `nankai_briefing`.

## Resources

Read-only reference documents a client can list and read without a tool call. Each is rendered from the same data the tools use, so they never drift out of sync.

| Resource | Content |
|---|---|
| `nankai://sources` | The official source registry — every agency cited, with URL, plus the standing disclaimer. |
| `nankai://headline-figures` | The 2025 scenario's headline figures, each with source, as-of date, and notes. |
| `nankai://shindo-scale` | The JMA intensity scale (震度 5弱–7) — what each level means for people and buildings. |
| `nankai://building-standards` | The 1981 新耐震 / 2000 wooden-house boundaries + 2016 Kumamoto field-damage data. |

## Example prompts

```
Brief me on the Nankai Trough earthquake — the scale, the reach, and what
intensity 7 actually means for a building.
```

```
My house is in 高知市本町. Give me the official hazard maps for my address's
predicted shaking and tsunami.
```

```
I live in a wooden house built in 1978. What seismic standard is that under,
and what should I do about it? Don't tell me whether it's safe.
```

```
Walk me through honestly assessing my home's earthquake risk:
静岡市葵区追手町9-6, built 1990, reinforced concrete.
```

## Scope — v1 vs v2

**v1 (this) does not compute a per-address Nankai intensity/tsunami value.** That data lives in bulk Cabinet Office GIS files that need an ingestion pipeline. Instead, `official_hazard_maps` bridges you to the official maps that already hold it. Computing it in-app is the deliberate **v2**.

## Headline figures (and where they come from)

Every figure below is verified against the primary government source and carries an as-of date in the tool output. See `src/data/nankai.ts` for the full verification log.

| Figure | Value | Source |
|---|---|---|
| 30-year probability | Two models since the 2025-09-26 revision: **60–90%+** / **20–50%**. Act on the higher. | 地震本部 |
| Worst-case deaths | ~298,000 (upper bound, flood defenses functioning) | 内閣府 2025-03 |
| Economic loss | ~¥270兆 (¥224.9兆 direct + ¥45.4兆 production); ~¥292兆 incl. transport disruption | 内閣府 2025-03 |
| Intensity 7 | Across 10 prefectures | 内閣府 2025-03 |
| Reach | 764 municipalities in 31 prefectures at 震度6弱以上 or 津波3m以上 | 内閣府 2025-03 |
| Tsunami | 5 m+ within minutes on the fastest coasts; max ~34 m (高知), ~31 m (静岡) | 内閣府 / 気象庁 |

## Sources & license

Official data is used as **derived output with attribution**; raw government files are **never re-hosted**.

出典：内閣府 南海トラフの巨大地震モデル・被害想定検討会 ／ 地震調査研究推進本部 ／ 気象庁 ／ 国土交通省（住まいの耐震化）／ 国土地理院（地理院タイル・ジオコーディング）／ 住宅リフォーム推進協議会。

## 日本語

南海トラフ地震のハザードと建物の耐震性を、公的データだけで正直に扱うMCPサーバーです。内閣府・地震本部・気象庁・国土交通省の公表値を、出典と日付つきで提示し、あなたの住所の正確な想定震度・津波は公式ハザードマップへ橋渡しします。建物の安全性は「安全／危険」と判定せず、建築年と構造から耐震基準の世代を示し、耐震診断・補助制度へ案内します。ローカル動作、APIキー不要。

## Disclaimer

This server surfaces official Japanese government data and explanations. It is not a prediction, not a verdict on whether you or your home are safe, and not a substitute for official evacuation guidance or a professional seismic diagnosis (耐震診断). Figures are approximate and as reported by their official sources; always confirm at the source. Unofficial — not affiliated with any government agency.

## License

[MIT](LICENSE)

---

## More MCPs

| MCP | What it does |
|-----|-------------|
| [Japan Design](https://github.com/mrslbt/japan-ux-mcp) | Enforces Japanese UI + UX conventions on real CSS/markup |
| [rippr](https://github.com/mrslbt/rippr) | YouTube transcript ripper for humans and AI agents |
| [Rakuten](https://github.com/mrslbt/rakuten-mcp) | Search Rakuten's marketplace, books, and hotels |

---

Built by [Marsel Bait](https://github.com/mrslbt) in Tokyo