F
licenseA
qualityD
maintenanceEnables 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.
3
21
CiNii MCP Server
by suzuuuuu09
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@CiNii MCP Serverfind articles about quantum computing published after 2020"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
CiNii MCP Server
Setup
uv sync --no-devPlease set the directory path and the CINII_APP_ID.
{
"mcpServers": {
"cinii-mcp-server": {
"command": "uv",
"args": [
"--directory",
"<YOUR_MCP_SERVER_DIRECTORY>",
"run",
"server.py"
],
"env": {
"CINII_APP_ID": "<YOUR_CINII_APP_ID>"
},
}
}
}Related MCP server: cinii-mcp
API Key Registration
Access CiNii API Registration
Find and access the link for "CiNii Web API Developer Registration".
Upon accessing, a registration form will appear. Fill in the necessary information and submit your application.
After submission, your Application ID will be sent to you via email.
Usage
Python API
from lib.cinii import CiNiiClient, SortOrder, SearchRange
client = CiNiiClient(appid="your_app_id")
# Basic search
results = client.advanced_search({
"query": "機械学習",
"max_results": 10
})
# Advanced search with filters
results = client.advanced_search({
"query": "Deep Learning",
"max_results": 20,
"sortorder": SortOrder.PUBLICATION_YEAR_DESC, # Publication year, descending
"range": SearchRange.HAS_BODY_IN_CINII, # The full text is available on CiNii.
"year_from": 2020,
"year_to": 2024
})
# Or you can also use numeric values for the search Options
results = client.advanced_search({
"query": "Deep Learning",
"max_results": 20,
"sortorder": 1, # Publication year, descending
"range": 1, # The full text is available on CiNii.
"year_from": 2020,
"year_to": 2024
})Sort Order Options
SortOrder.PUBLICATION_YEAR_DESC(1): Publication year descendingSortOrder.PUBLICATION_YEAR_ASC(2): Publication year ascendingSortOrder.TITLE_DESC(3): Title descendingSortOrder.TITLE_ASC(4): Title ascendingSortOrder.JOURNAL_DESC(5): Journal descendingSortOrder.JOURNAL_ASC(6): Journal ascendingSortOrder.CITATION_DESC(7): Citation count descending
Search Range Options
SearchRange.ALL(0): AllSearchRange.HAS_BODY_IN_CINII(1): Body exists in CiNiiSearchRange.HAS_BODY_OR_LINK(2): Body exists in CiNii, or link exists in linked services
Available Tools
1 tooladvanced_search_detailedC
CiNiiで高度な検索を行い、論文情報を取得する
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| issn | No | ||
| lang | No | ||
| page | No | ||
| issue | No | ||
| query | No | ||
| range | No | ||
| start | No | ||
| title | No | ||
| author | No | ||
| volume | No | ||
| journal | No | ||
| year_to | No | ||
| authorid | No | ||
| publisher | No | ||
| reference | No | ||
| sortorder | No | ||
| year_from | No | ||
| affiliation | No | ||
| max_results | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
C2.3/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden of disclosing behavioral traits. It only states the action and provides no information about read-only status, pagination, rate limits, authentication, or any side effects, leaving the agent completely uninformed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that wastes no words and front-loads the core action. However, it is so brief that it borders on under-specification, though that is better captured in completeness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 19 optional parameters, no schema descriptions, and no annotations, a one-sentence description is severely inadequate. The output schema exists but does not help the agent understand when or how to use the tool, making the description far from complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema contains 19 parameters with zero description coverage, and the description mentions none of them. Without any explanation of parameters like issn, lang, sortorder, or max_results, an agent cannot correctly construct a valid search query.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool performs an advanced search on CiNii and retrieves paper information, using a specific verb (検索を行い) and resource (CiNii). However, with no sibling tools listed, it does not differentiate beyond the basic action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, nor are there any use cases, prerequisites, or exclusions. The phrase 'advanced search' implies a general purpose but offers no concrete context for an agent to decide when to invoke it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
C2.8/5.0
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear from its name and description.
Naming Consistency5/5
The single tool uses a descriptive snake_case name that aligns with common MCP naming conventions. With only one tool, there are no inconsistencies to evaluate.
Tool Count3/5
One tool is on the low end and feels thin for a server named CiNii, which typically implies a richer API surface. However, the tool itself is comprehensive enough to perform advanced searches, so it's borderline.
Completeness2/5
The server only offers a single search tool. It lacks dedicated operations for fetching paper details by ID, managing result pagination, or accessing related resources like authors or references, leaving significant gaps for a full CiNii integration.
Maintenance
ActivityInactive
ResponsivenessNo issues
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Academic literature search, retrieval, and private library management on top of OpenAlex.
Scholarly search: OpenAlex, Crossref, arXiv, OpenCitations and PubMed in one endpoint.
Search PubMed/Europe PMC, fetch articles and full text (PMC/EPMC/Unpaywall), citations, MeSH terms.
Federated search of books and papers, BibTeX/RIS citations, open-access retrieval and reading.
Related MCP Servers
- AlicenseAqualityAmaintenanceEnables querying Japan's national academic database, CiNii Research, for articles, books, dissertations, KAKEN projects, and researcher profiles via seven MCP tools.72MIT
- AlicenseAqualityCmaintenanceEnables searching CiNii Research for academic articles, books, grants, and research data, and retrieving metadata for individual items.2MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to search and retrieve paper information from CNKI (China National Knowledge Infrastructure), supporting 15 search types, pagination, sorting, and detailed metadata extraction.31MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/suzuuuuu09/cinii-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server