Skip to main content
Glama

Related Servers

Alternatives to jp-terrain-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables users to query Japan's J-SHIS earthquake hazard probabilities and surface-ground amplification for specified latitude and longitude coordinates through read-only MCP tools.
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables access to Japan Meteorological Agency data through MCP, covering weather forecasts, warnings, earthquakes with seismic intensity, tsunami bulletins, and volcano alerts, with place-name lookup in kanji, kana, or romaji and no API key.
      7
      MIT
    • 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
      -
    • A
      license
      A
      quality
      D
      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
      47 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables users to search and retrieve Japanese statistical dashboard indicators, regions, terms, social events, surveys, and Bank of Japan time-series data through MCP tools, a CLI, and a Python library.
      10
      MIT

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools are cleanly separated by resource (elevation, geology, seismic hazard, ground amplification) and by point-vs-area or single-vs-batch scope. The weakest boundary is get_earthquake_hazard vs get_hazard_intensity, which both return seismic hazard at a point and differ only in which quantity is the input versus the output; descriptions do disambiguate them, but they will still invite misselection.

    Naming Consistency4/5

    All names use a consistent snake_case get_ verb prefix, with singular/plural (get_elevation(s)) and area_ (get_area_geology) modifiers used predictably to signal scope. The one minor inconsistency is get_hazard_intensity, which drops the 'earthquake_' qualifier used by its sibling get_earthquake_hazard.

    Tool Count5/5

    Seven tools is a well-scoped set for a read-only terrain/geology/hazard lookup server, with each tool covering a distinct dataset or access pattern. No tools appear redundant or padded.

    Completeness4/5

    The surface covers point and batched/area queries across elevation, geology, seismic hazard and ground amplification, which is solid read-only lifecycle coverage for this domain. Minor gaps exist: no area/box variant for elevation, no batching for hazard or geology points, and no metadata/list tool describing available datasets or parameter vocabularies.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues