cnki-search
Related Servers
Alternatives to cnki-search
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for deep CNKI academic search, retrieving multi-dimensional data (abstracts, keywords, references, citations, similar papers, keyword weights) and enabling citation network traversal via Playwright-based API interception.1623 PyPI15MIT
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server for searching Chinese academic papers and core journal information across multiple free platforms like Baidu Scholar and the National Center for Philosophy and Social Sciences. It enables users to retrieve metadata for social science and STEM research papers without requiring API keys.-
- FlicenseAqualityDmaintenanceEnables AI agents to search and retrieve academic papers from China National Knowledge Infrastructure (CNKI), supporting various search types including subject, keyword, author, and DOI lookups.321-
- AlicenseAqualityBmaintenanceEnables AI clients to run read-only Chinese literature metadata searches against CNKI through MCP tools, returning titles, authors, journals, years, citation counts, abstracts and DOI details. Supports keyword or fielded professional queries, paging, sorting, and RIS/EndNote text export while never downloading full texts or writing records into reference managers.541 PyPIMIT
- AlicenseAqualityDmaintenanceUnified academic search MCP server that searches open literature (arXiv, bioRxiv, medRxiv, PMC), CNKI, and Web of Science, with browser-backed authentication, local paper library, and export to multiple formats.212MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search, read, batch-download, and cite CNKI papers using institutional IP recognition or Shibboleth/CARSI single sign-on, with local PDF parsing, caching, and Zotero library lookup.17MIT
TDQS
Scored across 2 tools
The two tools are distinctly separated: 'search' performs queries across metadata fields, while 'get_record' fetches details from a specific URL returned by search. There is no functional overlap between them.
Both tool names follow a clear lowercase_with_underscores convention and use verb-first naming ('search', 'get_record'). The pattern is consistent and predictable.
With only two tools, the server is minimal. The scope (searching and retrieving CNKI records) is narrow enough to justify this count, but it borders on being too thin for a productive search API.
The server covers the essential metadata search and record retrieval workflows. It lacks features like citation export or full-text download, but for its stated purpose of metadata access, the coverage is adequate with only minor gaps.