Skip to main content
Glama
dataartai

네이버 API MCP 서버

by dataartai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to 네이버 API MCP 서버

No user-submitted related servers found.

    Related Servers

    • naver-mcp

      leedw80
      F
      license
      A
      quality
      C
      maintenance
      Naver Search API + Datalab API MCP server with 19 tools for Korean web search and trend analysis.
      19
      11 npm
      -

    • naver-search-mcp

      iamyaeeun
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Naver Search Open API, enabling search news, blog, and shop functionalities through natural language.
      -

    • Naver MCP Server

      pfldy2850
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides access to Naver OpenAPI services, enabling users to search blogs, news, books, images, and other content through standardized Model Context Protocol interfaces.
      114
      MIT

    • Aladin Book Search MCP Server

      TeeDDub
      A
      license
      A
      quality
      D
      maintenance
      MCP server that allows searching and retrieving book information from Aladin's book store API, including book details, bestseller lists, and category-based searches.
      9
      4
      MIT

    • Korea Housing MCP

      doorijaehyuk
      F
      license
      Not graded
      quality
      C
      maintenance
      This MCP server integrates South Korea's national law information, building registers from MOLIT, and KOSIS statistics for housing development research. It enables searching laws, retrieving building details, and accessing statistical data through natural language.
      -
    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

    C2.1/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a unique, clearly identifiable purpose: search tools target different Naver services (blog, kin, shopping, encyclopedia), while trend tools are differentiated by resource (keyword vs category) and dimension (age, device, gender). No two tools appear to overlap in function.

    Naming Consistency4/5

    Naming follows a predictable verb-noun-modifier pattern (search-<service> and get-<resource>-by-<dimension>/trends). However, there is a minor inconsistency between using 'search' for services and 'get' for trends, and the suffix 'trends' is not a dimension like 'by-age'. Overall still readable and systematic.

    Tool Count5/5

    With 12 tools, the server is well-scoped, covering a typical Naver API surface without being bloated. Each tool earns its place, and the count is within the ideal range for a focused MCP server.

    Completeness4/5

    The tool set covers primary Naver search services and trend analytics across multiple dimensions. Minor gaps include missing search services (e.g., web, news, image) and no explicit overall trend endpoint separate from the by-dimension variants, but the core domain is well represented.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources