原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Nankai Trough

作者:mrslbt版本 0.2.1i★ –i在你的电脑上运行
注册名称io.github.mrslbt/nankai-trough

安装

概览

作者提供的说明(英文原文)

Nankai Trough earthquake hazard & building-safety, from official Japan data. No verdicts.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月10日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 mrslbt 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 18952 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 18952 个服务器的 57% 更新
  • 基础检查结果等于或优于此分类中其他 18952 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Nankai Trough 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.2.1)于35天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Google Workspace MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者:formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者:desktop-commander正在增长★ 211今天更新

在云端运行✓ desktopcommander.app

Google Workspace MCP

Cross-client Google Workspace admin: 2SV gaps, license waste, sharing drift, safe offboarding.

作者:servosity非常新今天更新

在你的电脑上运行

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

nankai-trough-mcp

Nankai Trough (南海トラフ地震) earthquake hazard and 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.

Live companion map: https://nankaitrough.bymarsel.me (this is the open data engine behind it, the same official data as an explorable map).

⚠️ 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 cited and usable from an AI assistant, without ever inventing a number.

The attitude: assume the worst

The earthquake is unknown, and claiming we know is an illusion. So the refusal here is one-directional: the tools will alarm you with official numbers, and they will never reassure you.

Where the official model publishes several cases, the severe one leads. A low probability is reported as a floor, not a ceiling, and is never relayed as good news. location_probability will tell you the government puts your mesh at a 12% chance of 震度6強 in 30 years; it will not tell you that means you are fine.

If you cannot write Japanese

The official geocoder only reads Japanese addresses, which would have excluded the people this server is for. Give a 7-digit postal code instead and every address-taking tool resolves it through Japan Post data:

232-0063        2320063        〒232-0063

That lands on the centre of your postal district rather than your building, and the tools say so in the response rather than pretending to more precision than they have. All output is available in English with language: "en".

Data rules

  • 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

claude mcp add nankai -- npx -y nankai-trough-mcp
JSON config

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

Claude Code: ~/.claude/.mcp.json

{

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

Cursor: ~/.cursor/mcp.json

{

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

VS Code (GitHub Copilot): .vscode/mcp.json

{

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

Claude Desktop: claude_desktop_config.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
From source
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:

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

Tools

ToolDescription
nankai_overviewThe official 2025 scenario's scale and reach (probability, casualties, intensity-7 reach, tsunami), each with its source. Start here.
official_hazard_mapsAddress → 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_checkBuild year + structure → 旧耐震 / 新耐震 / 2000-standard classification with context. Not a verdict.
taishin_subsidy_guideRoutes to subsidised, often-free 耐震診断 / 耐震補強 programs and the national support framework.
shindo_meaningWhat a JMA intensity (震度 5弱–7) means for people and buildings, on the official 気象庁 scale.
location_probabilityAddress → the official J-SHIS 30-year probability of reaching each JMA intensity at that ~250m mesh, severe case first. All-source probabilistic (地震本部), not the Nankai scenario. Reported, never computed.
preparedness_planHousehold details → a sourced plan: stockpile sized to the official one-week guidance, what to do now, what to do when it shakes, and the structural route. An officially recommended floor, not a verdict on survival.
geocode_addressAddress → 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.

ResourceContent
nankai://sourcesThe official source registry: every agency cited, with URL, plus the standing disclaimer.
nankai://headline-figuresThe 2025 scenario's headline figures, each with source, as-of date, and notes.
nankai://shindo-scaleThe JMA intensity scale (震度 5弱–7): what each level means for people and buildings.
nankai://building-standardsThe 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 assessing my home's earthquake risk: 静岡市葵区追手町9-6, built 1990, reinforced concrete.

Scope

This server does not compute its own per-address values. Two different things follow from that:

  • It reports official published per-mesh probabilities (location_probability, J-SHIS Y2024). Surfacing a government figure is not inventing one.
  • It bridges to the official maps for the Nankai scenario at an address (official_hazard_maps). That data lives in bulk Cabinet Office GIS files needing an ingestion pipeline, and faking it is not on the table.

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.

FigureValueSource
30-year probabilityTwo 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 7Across 10 prefectures内閣府 2025-03
Reach764 municipalities in 31 prefectures at 震度6弱以上 or 津波3m以上内閣府 2025-03
Tsunami5 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


More MCPs

MCPWhat it does
Japan DesignEnforces Japanese UI + UX conventions on real CSS/markup
ripprYouTube transcript ripper for humans and AI agents
RakutenSearch Rakuten's marketplace, books, and hotels

Built by Marsel Bait in Tokyo

问 PopNx