io.github.mrslbt/nankai-trough
NPM · NANKAI-TROUGH-MCP · SCANNED SEP 20
Nankai Trough earthquake hazard & building-safety, from official Japan data. No verdicts.
Available components
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 25 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability88
- 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 Management90
- Stability observed for 27 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
Tool Safety50
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "NEVER tell the user", at byte 198 of that field. See how to fix → Fail
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.mrslbt/nankai-trough MCP server?
io.github.mrslbt/nankai-trough runs locally as an npm package, launched with npx -y nankai-trough-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · nankai-trough-mcp
claude mcp add mrslbt-nankai-trough -- npx -y nankai-trough-mcp
{
"mcpServers": {
"mrslbt-nankai-trough": {
"command": "npx",
"args": [
"-y",
"nankai-trough-mcp"
]
}
}
} {
"servers": {
"mrslbt-nankai-trough": {
"command": "npx",
"args": [
"-y",
"nankai-trough-mcp"
]
}
}
} codex mcp add mrslbt-nankai-trough -- npx -y nankai-trough-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mrslbt-nankai-trough": {
"type": "local",
"command": [
"npx",
"-y",
"nankai-trough-mcp"
],
"enabled": true
}
}
} openclaw mcp add mrslbt-nankai-trough --command npx --arg -y --arg nankai-trough-mcp
mcp_servers:
mrslbt-nankai-trough:
command: "npx"
args: ["-y", "nankai-trough-mcp"] {
"McpServers": {
"mrslbt-nankai-trough": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"nankai-trough-mcp"
]
}
}
} assistant mcp add mrslbt-nankai-trough -t stdio -c npx -a -y nankai-trough-mcp
{
"mcpServers": {
"mrslbt-nankai-trough": {
"command": "npx",
"args": [
"-y",
"nankai-trough-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/nankai-trough-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
building_seismic_check Building Seismic-Standard 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.
| Name | Type | Req | Description |
|---|---|---|---|
| build_year | integer | yes | Year the building's 建築確認 (building confirmation) was issued, roughly its build year. |
| language | string | – | Output language: 'en', 'ja', or 'both' (default). |
| structure | string | yes | Building structure: wood (木造), reinforced_concrete (RC), steel (鉄骨), or other. |
No output schema declared.
No examples provided.
geocode_address Geocode a Japanese 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Japanese address to geocode. |
No output schema declared.
No examples provided.
nankai_overview Nankai Trough Scale & Reach ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Output language: 'en', 'ja', or 'both' (default). |
No output schema declared.
No examples provided.
official_hazard_maps Official Hazard Maps for an Address ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Japanese address, e.g. '静岡県静岡市葵区追手町9-6' or '高知市本町5'. |
| language | string | – | Output language: 'en', 'ja', or 'both' (default). |
No output schema declared.
No examples provided.
shindo_meaning JMA Seismic Intensity (震度) 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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Output language: 'en', 'ja', or 'both' (default). |
| shindo | string | yes | JMA intensity: '5-' (5弱), '5+' (5強), '6-' (6弱), '6+' (6強), or '7'. |
No output schema declared.
No examples provided.
taishin_subsidy_guide Seismic Diagnosis & Retrofit 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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Output language: 'en', 'ja', or 'both' (default). |
| location | string | – | Optional municipality or prefecture to tailor the search hint, e.g. '高知市' or '静岡県'. |
No output schema declared.
No examples provided.
What is the io.github.mrslbt/nankai-trough MCP server?
io.github.mrslbt/nankai-trough is an MCP server listed in the public MCP registry as io.github.mrslbt/nankai-trough. Nankai Trough earthquake hazard & building-safety, from official Japan data. No verdicts. This page covers its npm package (nankai-trough-mcp).
Is the io.github.mrslbt/nankai-trough MCP server safe to use?
io.github.mrslbt/nankai-trough scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.mrslbt/nankai-trough MCP server expose?
io.github.mrslbt/nankai-trough exposes 6 tools: nankai_overview, official_hazard_maps, building_seismic_check, taishin_subsidy_guide, shindo_meaning, geocode_address. Their descriptions and schemas cost roughly 669 tokens of context every time the server is loaded.
Is the io.github.mrslbt/nankai-trough MCP server still maintained?
io.github.mrslbt/nankai-trough is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mrslbt/nankai-trough MCP server under?
io.github.mrslbt/nankai-trough declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.