Skip to main content
Glama
Sign In
jp-statistics-mcp

jp-statistics-mcp

by koizumikento
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to jp-statistics-mcp

No user-submitted related servers found.

    Related Servers

    • estat-mcp

      ajtgjmdjp
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Japan's e-Stat (Government Statistics Portal). Search statistical datasets, retrieve data tables, and access metadata from official Japanese government statistics.
      39 PyPI
      10
      Apache 2.0

    • jp-procurement-mcp

      koizumikento
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching Japanese public procurement notices and contract award records, including summarizing awards, through MCP tools, a CLI, and a Python library without requiring an API key.
      MIT

    • e-stat-dashboard-mcp

      koizumikento
      A
      license
      B
      quality
      C
      maintenance
      Enables read-only search of indicator names to find series codes and retrieval of statistical values by series code, optionally filtered by region and period, through Japan's Statistics Dashboard API.
      2
      MIT

    • boj-stats-mcp

      koizumikento
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching Bank of Japan time-series statistics series by name or series code and retrieving time-series data for a specified series code and period through the official BOJ statistics API.
      MIT

    • e-Stat MCP

      koizumikento
      A
      license
      C
      quality
      B
      maintenance
      Enables access to Japan's official government statistics portal (e-Stat) API to search, retrieve, and analyze statistical data including census data, economic indicators, and demographic information across 17 statistical fields.
      13
      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

    B3.1/5.0

    Scored across 10 tools

    Disambiguation3/5

    The six search_* tools are cleanly separated by entity (indicator, region, term, social event, survey, series), but the data-fetch tools overlap: get_series_data, get_multiple_series_data, get_series_data_by_layer and get_indicator_data all sound like 'get time series data' and only the descriptions reveal that two are BOJ-series based and two are e-Stat layer/indicator based. The shared word 'series' across both e-Stat and BOJ tools invites misselection.

    Naming Consistency4/5

    All tools are snake_case with a verb_noun shape (search_*, get_*_data), so the pattern is predictable. Minor deviations: get_series_data_by_layer and get_multiple_series_data are longer qualified variants, and get_indicator_data lacks the 'series/indicator' symmetry with its siblings.

    Tool Count4/5

    Ten tools is a well-scoped count for a server spanning two data sources (e-Stat catalog entities plus BOJ series). Each tool maps to a distinct entity or fetch mode, with no obviously redundant entries.

    Completeness3/5

    There is search coverage for indicators, regions, terms, events, surveys and BOJ series plus data retrieval, but gaps remain: no tool to enumerate available databases/layers (the layer path required by get_series_data_by_layer and the 'one DB' required by get_multiple_series_data must come from outside the toolset), and no metadata/definition lookup for a BOJ series beyond the name search. Pagination via NEXTPOSITION is handled for only two of the fetch tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources