Skip to main content
Glama
datagokr-dev

datagokr

by datagokr-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to datagokr

No user-submitted related servers found.

    Related Servers

    • k-skill-korea

      taeyoung1005
      F
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server providing access to various Korean public data such as subway arrivals, weather, fine dust, bike availability, real estate, and more.
      -

    • vivory-mcp

      jayjodev
      F
      license
      Not graded
      quality
      D
      maintenance
      Korean public-data MCP servers for AI agents, enabling natural language queries to KOSIS statistics and other Korean official data sources without requiring local accounts or API keys.
      -

    • MCPortal

      yonghwan1106
      A
      license
      Not graded
      quality
      A
      maintenance
      Bridges Korean public data APIs (data.go.kr) into MCP with automatic OpenAPI normalization, quota management, caching, and backoff. Enables natural language interaction with Korean government data through MCP.
      71 PyPI
      Apache 2.0

    • open-ALIO-mcp

      gitbosung
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Korean public institution information, enabling AI clients to search, compare, and analyze disclosure data, public services, laws, and news.
      32
      1
      MIT

    • Seoul OpenData MCP

      whchoi98
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that provides access to Seoul's real-time city data (population, transit, air quality, weather, cultural events, etc.) and batch statistics, enabling natural language queries about Seoul. It also includes a catalog of raw Seoul Open Data Plaza datasets.
      19
      1
      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

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have distinct roles: search vs fields, login vs login_status, apply vs download. However, preview, get, and fetch all retrieve row/access information and could be confused despite clarifying notes about credentials and saving.

    Naming Consistency3/5

    All names are lowercase snake_case, but the pattern is mixed: several bare verbs (get, fetch, apply) alongside nouns (fields, login_status) with no consistent verb_noun convention. Still readable, but not predictable.

    Tool Count5/5

    10 tools is well within the ideal range for this server's purpose. Each tool covers a distinct phase of the public-data workflow (auth, discovery, inspection, retrieval, application) and none feels redundant.

    Completeness4/5

    The surface covers login, discovery, metadata inspection, preview, access application, API/file retrieval, and download, forming a complete workflow. A minor gap remains: there is no explicit tool for listing or tracking submitted applications beyond the apply return value.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources