nl-openapi-mcp
Related Servers
Alternatives to nl-openapi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceExposes KCI and OAK Korean bibliographic services as MCP tools for searching, harvesting, and retrieving articles, references, and journal metrics.81MIT
- AlicenseAqualityAmaintenanceSearch and collect data from the National Assembly Library of Korea's OpenAPI (21 DB types) and export to xlsx/csv/json/sqlite.61MIT
- 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
- AlicenseAqualityAmaintenanceEnables searching and collecting academic literature metadata from KISTI ScienceOn via Claude or CLI, supporting various document types and export formats.51MIT
- AlicenseAqualityAmaintenanceEnables searching and harvesting Korean Citation Index literature, citation indices, and references via REST API and OAI-PMH.74MIT
- AlicenseAqualityAmaintenanceMCP server for searching and accessing Korean public data from data.go.kr, enabling dataset search, metadata lookup, and data retrieval/download via Python API or CLI.1024 PyPIMIT
TDQS
Scored across 3 tools
Each tool has a distinct purpose: nl_status verifies connectivity, nl_search performs a single query, and nl_collect aggregates multiple searches with saving and partitioning. Though nl_search and nl_collect both search, their roles are clearly separated (single vs. batch), so an agent cannot confuse them.
All tool names share the consistent 'nl_' prefix and lowercase_snake_case format. While 'status' is a noun and 'search'/'collect' are verbs, the naming is predictable and each name directly reflects its function, making the pattern easy to infer.
Three tools is a well-scoped count for a library search MCP, providing essential operations without redundancy. Each tool carries substantial functionality, especially nl_collect which bundles complex features like recursive partitioning and filtering, so every tool earns its place.
The set covers the full lifecycle of searching and collecting library records: health check, individual search, and batch collection with export options. It also addresses API limitations (e.g., 500-record cap) through built-in partitioning and provides explicit workarounds, leaving no obvious gaps for the stated domain.