cinii-mcp
Related Servers
Alternatives to cinii-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables searching CiNii Research for academic articles, books, grants, and research data, and retrieving metadata for individual items.2MIT
- AlicenseCqualityDmaintenanceEnables searching and retrieving academic articles from CiNii, Japan's largest bibliographic database, with support for advanced filtering, sorting, and search range options.11Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables LLMs and compatible clients to search academic papers, retrieve detailed metadata and abstracts, access full-text content when available, and perform topic searches with optional date filters via MCP tools.-
- FlicenseNot gradedqualityAmaintenanceEnables users to search academic papers, analyze citation networks, retrieve author details and publication histories, and get paper recommendations through a unified MCP interface.-
- FlicenseNot gradedqualityAmaintenanceEnables searching and retrieving academic papers, author profiles, citation and reference networks, recommendations, and related metadata from the Semantic Scholar API through MCP tools.-
- AlicenseAqualityBmaintenanceAn 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.30502 npm8MIT
TDQS
Scored across 11 tools
Tools are partitioned mostly by record type (books, articles, dissertations, data, kaken, researchers, libraries, holdings), which gives clear primary boundaries. The main overlap is between cinii_search_all, cinii_search_kaken, and cinii_search_projects_and_products, which all return mixed/project records and require reading descriptions to choose correctly; well-written descriptions mitigate this rather than eliminate it.
Every tool follows the same cinii_<verb>_<noun> snake_case pattern: search_books, search_articles, get_holdings, get_record, etc. Verbs are used consistently (search_ for queries, get_ for single-resource fetches), so the convention is fully predictable.
Eleven tools map cleanly onto the distinct CiNii content types plus the two NACSIS-CAT auxiliary operations (holdings, libraries) and a single-record fetch. Each tool has a recognizable domain slice and none appear redundant enough to remove.
The surface covers search across all major record types, single-record retrieval by CRID/URL, ISBN/NCID lookup, library lookup, and holdings — a coherent discovery lifecycle. Minor gaps exist (no citation/export or bulk record retrieval, no explicit researcher-by-ID fetch aside from search), but agents can work around these.