Skip to main content
Glama
lhs1152-lgtm

kcsc-design-mcp

by lhs1152-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to kcsc-design-mcp

No user-submitted related servers found.

    Related Servers

    • 갈피 법령조회 MCP

      uscaidev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search and retrieve Korean laws, regulations, administrative rules, legal interpretations, and precedents via official APIs for legal review workflows.
      1
      MIT

    • KJH Law MCP

      Ramhori
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search, retrieve, and analyze South Korean legal documents including statutes, precedents, constitutional decisions, and administrative rulings via the Ministry of Government Legislation Open API. Provides 89 specialized tools with features like legal abbreviation auto-recognition, annex extraction, and complex research chain workflows.
      MIT

    • Korean Stats MCP

      nagyeop
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to retrieve real-time official Korean statistics from the KOSIS database through natural language queries, with source citations.
      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 13 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search by name vs. full-text grep, outline vs. read vs. formula retrieval, audit vs. version check, and the design_* tools each handle a different aspect (list, map, flow, validate, stamp, template). No two tools could be confused even without reading descriptions in detail.

    Naming Consistency5/5

    All tools follow a consistent pattern: either kcsc_<action> (search, outline, read, formula, grep, audit, version) or design_<noun/action> (flows, map, flow, validate, stamp, template). The prefix group is uniform, and the second part is a clear, consistent descriptor.

    Tool Count5/5

    13 tools is well within the ideal 3–15 range. The count reflects the domain's needs: 7 tools for standards retrieval/verification and 6 for design flow management, each earning its place without redundancy.

    Completeness5/5

    The tool surface covers the full lifecycle of standards lookup (search, outline, read, formula, grep), verification (audit, version), and design flow management (list, map, detailed steps, validation, stamping, template generation). Any gaps, like edit/delete of flows, are handled externally since flows are YAML files, and the deliberate separation of formula retrieval from reading addresses the image limitation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources