Skip to main content
Glama
Sign In
e-stat-dashboard-mcp

e-stat-dashboard-mcp

by koizumikento
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to e-stat-dashboard-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • egov-data-mcp

      koizumikento
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Japan's e-Gov open data catalog through its official API, allowing keyword dataset searches and retrieval of dataset details and distribution URLs.
      MIT

    • OECD MCP Server

      cyanheads
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching, exploring, and querying over 1,500 OECD statistical datasets via SDMX, covering national accounts, employment, trade, PISA, health, and more.
      519 npm
      4
      Apache 2.0
    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/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools serve clearly distinct purposes: one searches for indicator codes by text, the other fetches series data for a given indicator. There is no overlap in function, so misselection is unlikely.

    Naming Consistency5/5

    Both names follow a consistent verb_noun snake_case pattern (search_indicators, get_indicator_data). The terminology around 'indicator' is also consistent across both.

    Tool Count3/5

    Two tools is thin for a statistics dashboard server; search and data retrieval are covered, but discoverability or metadata tasks have no dedicated entry point. It is borderline rather than clearly mismatched, since the domain is narrow.

    Completeness3/5

    The core lookup-then-fetch workflow is covered, but there is no way to list available datasets, browse indicators without a text query, or retrieve metadata (units, definitions). These gaps are workable but notable for a data exploration server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources