Skip to main content
Glama
ckgerteis

ndl-mcp

by ckgerteis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ndl-mcp

No user-submitted related servers found.

    Related Servers

    • houan-mcp

      SHAYOUWORLD
      A
      license
      A
      quality
      B
      maintenance
      MCP server for searching Japanese Diet bills and committee Q\&A records via the NDL Kokkai API.
      4
      221 npm
      1
      MIT

    • kokkai-giji-mcp

      seiichi3141
      F
      license
      B
      quality
      D
      maintenance
      MCP server that provides tools and prompts for searching Japanese Diet (国会) proceedings using the National Diet Library API. Enables querying meetings and speeches with various filters and obtaining direct URLs to the records.
      3
      38
      -

    • jp-lit-mcp

      itarunnn
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for Japanese literature research that provides unified search across NDL, CiNii, J-STAGE, and other Japanese academic databases, with Skills to assist in search planning and result evaluation.
      30
      46 npm
      7
      MIT

    • openalex-mcp

      ckgerteis
      A
      license
      A
      quality
      A
      maintenance
      MCP server for the OpenAlex scholarly graph API, enabling searches for authors, works, institutions, sources, and citation data. Supports optional query logging with hash-chained receipts.
      8
      1
      MIT

    • kanpou-mcp

      yoshinaga2015
      F
      license
      B
      quality
      D
      maintenance
      MCP server for searching Japanese government procurement notices via the Kanpou API. Enables LLMs to search by date, keyword, or detailed criteria.
      3
      1
      -
    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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each search tool targets a distinct NDL dataset or scope, and get_record is clearly separate as an ID-based fetch. The main ambiguity is between ndl_search_books and ndl_search_national_bibliography, since both can return book-like records, though their descriptions clarify holdings vs. authority data.

    Naming Consistency5/5

    All tool names follow a predictable ndl_<action>_<scope> pattern: get_record and search_* for the rest. This makes the set easy to navigate and avoids stylistic mixing.

    Tool Count5/5

    Six tools is well-scoped for the server's purpose: one record retrieval tool and five search tools covering separate NDL data sources plus a combined search. No tool feels redundant or out of place.

    Completeness4/5

    The set covers the main NDL search surfaces and record retrieval by ID, which supports core bibliographic workflows. The main minor gap is that only the open Digital Collections subset is exposed, while wider digital collection content is not covered by a dedicated tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources