Skip to main content
Glama
NSLC7779

korea-health-mcp-server

by NSLC7779
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to korea-health-mcp-server

No user-submitted related servers found.

    Related Servers

    • kosis-mcp

      updown256
      A
      license
      Not graded
      quality
      B
      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

    • Nonpayment Health MCP Server

      chweyun
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying and analyzing non-reimbursable medical treatment costs in South Korea using the Health Insurance Review & Assessment Service API. Supports searching treatment codes, comparing hospital prices, regional statistics analysis, and finding cost-effective healthcare options.
      -

    • korea-public-data-mcp

      GeeYun086
      F
      license
      A
      quality
      B
      maintenance
      Enables Claude to query Korean public financial, economic, and statistical data (OpenDART, ECOS, KOSIS, and data.go.kr) via real API calls, providing factual answers instead of guesses.
      13
      -
    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

    Disambiguation5/5

    Each tool targets a specific resource and action: hospital search vs. hospital details, non-payment by region vs. by hospital, drug info vs. DUR safety, disease statistics, plus two clearly distinct meta-tools for discovery and execution. No overlapping purposes.

    Naming Consistency4/5

    Domain tools consistently follow a 'kohealth_verb_noun' pattern (e.g., search_hospital, get_hospital_info, get_drug_dur). The two meta-tools (discover_tools, execute_tool) deviate from this pattern but are clearly named and serve a different function, so the inconsistency is minor.

    Tool Count5/5

    With 10 tools, the server is well-scoped. It covers multiple health data domains (hospitals, non-payment, drugs, diseases) without unnecessary bloat, and each tool contributes meaningfully to the overall functionality.

    Completeness4/5

    The tool surface provides comprehensive coverage for the apparent domain: hospital search and detailed info, non-payment item lookup by region and hospital, drug search and DUR safety, and disease statistics. A minor gap is the lack of a tool to directly compare non-payment prices across multiple hospitals, but the existing search can partially achieve this.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources