Skip to main content
Glama
Sign In
nl-openapi-mcp

nl-openapi-mcp

by rubatoyd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to nl-openapi-mcp

No user-submitted related servers found.

    Related Servers

    • io.github.rubatoyd/kakao-book

      rubatoyd
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      4
      1
      MIT

    • scienceon-mcp

      rubatoyd
      A
      license
      A
      quality
      B
      maintenance
      Enables searching and collecting academic literature metadata from KISTI ScienceOn via Claude or CLI, supporting various document types and export formats.
      5
      1
      MIT

    • kci-openapi-mcp

      rubatoyd
      A
      license
      A
      quality
      B
      maintenance
      Enables searching and harvesting Korean Citation Index literature, citation indices, and references via REST API and OAI-PMH.
      7
      4
      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.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources