Skip to main content
Glama
rubatoyd

io.github.rubatoyd/kosis-openapi-mcp

by rubatoyd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to io.github.rubatoyd/kosis-openapi-mcp

No user-submitted related servers found.

    Related Servers

    • ne-kosis-mcp

      neneungyul2
      A
      license
      A
      quality
      C
      maintenance
      Enables searching, retrieving, and analyzing South Korean national statistics through the KOSIS OpenAPI, including trend, change-rate, and CAGR calculations. Results can be explored by topic or organization and exported to Excel or CSV.
      7
      MIT

    • kosis-kr

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables browsing, searching, and pulling time series from Statistics Korea's KOSIS database, covering ~100,000 tables on population, prices, employment, trade, and industry.
      7 npm
      MIT

    • korea-bok-stats-mcp

      hlucent
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying Bank of Korea ECOS economic statistics via Open API, including searching tables, retrieving time series data, and accessing key indicators.
      MIT

    • Korea Stats MCP

      Dayoooun
      A
      license
      A
      quality
      B
      maintenance
      Enables natural language querying of Korean statistical data from KOSIS, including population, employment, GDP, housing prices, and more, with support for regional and trend analysis.
      8
      5 npm
      17
      MIT

    • kosis-mcp

      updown256
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Korean official statistics from KOSIS via natural language in MCP clients like Claude Desktop, wrapping the KOSIS OpenAPI for search, data retrieval, and metadata exploration.
      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/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a single clear role: table search vs indicator search, table data vs indicator data, metadata vs survey explanation, data retrieval vs file export. The detailed descriptions explicitly distinguish the similar indicator/table families, so an agent can reliably choose between them.

    Naming Consistency4/5

    All tools share the kosis_ prefix and snake_case, and the search/data pairs are parallel (kosis_search/kosis_indicator_search, kosis_data/kosis_indicator_data). However, the second part mixes bare verbs (search, list, explain, collect) with bare nouns (meta, data, citation, guide), so it is not a strict verb_noun convention.

    Tool Count5/5

    11 tools is well within the ideal range and each one earns its place: status/guide for orientation, search/explain/list/meta/data for the table workflow, indicator_search/indicator_data for the indicator workflow, plus collect and citation for output and scholarship.

    Completeness5/5

    For a read-only statistical data API, the surface is complete: users can discover tables by search or tree, read survey descriptions and table metadata, fetch full table data with automatic axis/period handling, access major indicators, export to files, and generate citations. No obvious dead ends or missing core operations remain.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources