na-openapi-mcp
Related Servers
Alternatives to na-openapi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables searching and collecting 72 types of Korean legal information from the National Law Information Center Open API, including statutes, precedents, administrative rules, local ordinances, legal interpretations, and committee decisions, and exporting results to xlsx, csv, json, or sqlite.6MIT
- AlicenseAqualityAmaintenanceEnables searching the Kakao Daum Book Search API by title, author, publisher, or ISBN, retrieving detailed bibliographic and pricing metadata, and exporting results to xlsx, csv, json, or sqlite through MCP or CLI.41MIT
- AlicenseAqualityAmaintenanceSearch and harvest Korean academic literature and book bibliography metadata from the National Library of Korea Seoji OpenAPI via MCP or CLI.31MIT
- AlicenseAqualityAmaintenanceEnables searching and collecting academic literature metadata from KISTI ScienceOn via Claude or CLI, supporting various document types and export formats.51MIT
- AlicenseAqualityAmaintenanceEnables book search and detailed bibliographic queries via the Aladin Open API, including original titles, table of contents, page counts, dimensions, used-book prices, and bestseller lists, with batch collection to Excel/CSV.5MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access real-time legislative data from the Korean National Assembly including members, bills, votes, and schedules through 276 Open APIs. Supports dual transport modes (stdio/HTTP), configurable Lite/Full tool profiles, and in-memory caching for efficient querying.5 npm91MIT
TDQS
Scored across 6 tools
Each tool targets a distinct operation: health check, search, single-record detail, union collection/export, table of contents, and field validation. Even where na_search and na_collect both query, the descriptions clearly separate raw querying from OR aggregation and saving results.
All tools share the na_ prefix and use clear lowercase names, which makes the set feel coherent. However, the pattern mixes verbs (search, collect) with nouns/abbreviations (status, detail, toc, fields), so it is not perfectly uniform.
Six tools is a well-scoped size for this read-only library search API. Each tool earns its place by covering a distinct capability without unnecessary duplication.
The surface covers the main workflows: checking access, searching, retrieving item-level detail, harvesting OR-combined results, getting TOC data, and discovering valid field/dbname values. There are no obvious dead ends for the stated domain.