Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.mrslbt/nankai-trough

NPM · NANKAI-TROUGH-MCP · SCANNED AUG 3

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

Available components

+18 this week 70 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1226 tokens (~122/item across 10 items; 6 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · nankai-trough-mcp

# add to Claude Code
claude mcp add mrslbt-nankai-trough -- npx -y nankai-trough-mcp
# add to Codex CLI
codex mcp add mrslbt-nankai-trough -- npx -y nankai-trough-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrslbt-nankai-trough": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "nankai-trough-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mrslbt-nankai-trough --command npx --arg -y --arg nankai-trough-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mrslbt-nankai-trough:
    command: "npx"
    args: ["-y", "nankai-trough-mcp"]
// mcp.json
{
  "mcpServers": {
    "mrslbt-nankai-trough": {
      "command": "npx",
      "args": [
        "-y",
        "nankai-trough-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +65
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • MCP protocol: unverified → pass functional
    • Maintenance: unverified → pass functional
    • Stability: unverified → 0.20 functional
    • License: unverified → pass functional
    • Schema quality: unverified → excellent functional
    • Dependency health: unverified → partial functional
    • Schema quality: unverified → 100 functional
    • Tool coverage: unverified → 100 functional
    • Licence: MIT functional
    • Package version: 0.1.0 → 0.1.1 functional
  • 1 Aug 26 −29
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 52

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~669 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
building_seismic_check ~150

Classify a building's seismic standard (旧耐震 / 新耐震 / 2000 wooden standard) from a build year and structure the USER provides, with risk context. This is NOT a safety verdict; direct the user to a professional 耐震診断 via taishin_subsidy_guide.

NameTypeReqDescription
build_yearintegeryesYear the building's 建築確認 (building confirmation) was issued, roughly its build year.
languagestringOutput language: 'en', 'ja', or 'both' (default).
structurestringyesBuilding structure: wood (木造), reinforced_concrete (RC), steel (鉄骨), or other.

No output schema declared.

No examples provided.

geocode_address ~66

Convert a Japanese address to coordinates (lat/lon) and parse the prefecture/municipality, via the official GSI geocoder. Utility used by official_hazard_maps; call it directly when you only need coordinates.

NameTypeReqDescription
addressstringyesJapanese address to geocode.

No output schema declared.

No examples provided.

nankai_overview ~87

Get the headline facts of the official 2025 Nankai Trough estimate (probability, worst-case casualties/loss, intensity-7 reach, tsunami) with sources. Start here to understand the scale; then call official_hazard_maps for a specific address.

NameTypeReqDescription
languagestringOutput language: 'en', 'ja', or 'both' (default).

No output schema declared.

No examples provided.

official_hazard_maps ~121

Geocode a Japanese address and return links to the OFFICIAL government hazard maps that hold the exact per-address values (predicted intensity, tsunami inundation, your municipal map). This server does not compute those itself; it bridges you to the authoritative source.

NameTypeReqDescription
addressstringyesJapanese address, e.g. '静岡県静岡市葵区追手町9-6' or '高知市本町5'.
languagestringOutput language: 'en', 'ja', or 'both' (default).

No output schema declared.

No examples provided.

shindo_meaning ~123

Explain what a JMA seismic intensity level (5弱–7) actually means for people and buildings, using the official 気象庁 scale. The Nankai scenario projects up to intensity 7 across 10 prefectures.

NameTypeReqDescription
languagestringOutput language: 'en', 'ja', or 'both' (default).
shindostringyesJMA intensity: '5-' (5弱), '5+' (5強), '6-' (6弱), '6+' (6強), or '7'.

No output schema declared.

No examples provided.

taishin_subsidy_guide ~122

Route the user to subsidised/often-free seismic diagnosis (耐震診断) and retrofit (耐震補強) programs via the national directory, and explain the support framework. Amounts vary by municipality, so this routes and explains; it never quotes a figure.

NameTypeReqDescription
languagestringOutput language: 'en', 'ja', or 'both' (default).
locationstringOptional municipality or prefecture to tailor the search hint, e.g. '高知市' or '静岡県'.

No output schema declared.

No examples provided.