Skip to main content
Glama
mrslbt

nankai-trough-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nankai-trough-mcp

No user-submitted related servers found.

    Related Servers

    • gachi-data

      eng213035
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides Japanese station accessibility and hazard data via MCP tools, including toilet information, public toilet locations, and official hazard categories.
      1
      -

    • jp-data-mcp

      kimotostudio
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Japanese public business data, enabling AI agents to validate and look up corporate numbers, search bank/branch codes, and check national holidays. Runs locally with no telemetry; live corporate registry data requires a free NTA app ID.
      8
      MIT

    • seismic-mcp

      hoon1983
      A
      license
      A
      quality
      D
      maintenance
      A unified MCP server that queries 20 seismic agencies in parallel, reconciles cross-agency earthquake reports, and surfaces discrepancies for AI agents.
      7
      1
      MIT

    • geojp-mcp

      55tarkun
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Japanese address and parcel lookup using ReverseGeoJP and ChibanJP APIs, enabling AI agents to convert coordinates to addresses and vice versa.
      4
      26 npm
      MIT

    • wems-mcp-server

      heliosarchitect
      A
      license
      Not graded
      quality
      D
      maintenance
      A powerful MCP server that connects AI assistants to authoritative natural hazard data sources, enabling monitoring of earthquakes, tsunamis, volcanoes, and solar events with configurable alerts and webhooks.
      1
      MIT

    • nor-data/nve-mcp

      3121n
      A
      license
      A
      quality
      D
      maintenance
      MCP server that wraps NVE's open GIS data to provide flood risk and landslide risk point lookups, with explicit uncertainty reporting (e.g., 'no data' vs 'safe') and source references.
      2
      38 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: overview facts, hazard map lookups, building seismic classification, subsidy routing, intensity scale education, and geocoding. The descriptions explicitly differentiate related tools (e.g., geocode_address is a utility used by official_hazard_maps, and building_seismic_check directs users to taishin_subsidy_guide). No two tools appear to do the same thing.

    Naming Consistency3/5

    All names use snake_case, but the structural pattern is inconsistent: some are noun phrases (nankai_overview, official_hazard_maps, shindo_meaning), some are compound nouns (building_seismic_check, taishin_subsidy_guide), and one is a verb phrase (geocode_address). The naming is readable and domain-oriented, but lacks the uniform verb_noun or noun_verb convention seen in higher-coherence server sets.

    Tool Count5/5

    With 6 tools, the count is well within the ideal 3-15 range and matches the server's scope of providing Nankai Trough earthquake information and guidance. Each tool fills a distinct role without unnecessary redundancy or clutter.

    Completeness4/5

    The tool set covers the core user journey: get headline facts, look up official hazard maps for an address, check a building's seismic standard, receive subsidy guidance, and understand intensity levels. Minor gaps exist, such as no dedicated tool for evacuation planning or real-time alerts, but these are not explicitly part of the stated domain and the existing tools form a coherent workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources