crossref-mcp
Related Servers
Alternatives to crossref-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search academic literature and retrieve detailed metadata for papers, journals, and funding organizations via the Crossref database. It supports DOI-based lookups and keyword searches to facilitate programmatic access to scholarly research data.7-
- AlicenseNot gradedqualityBmaintenanceEnables searching academic papers, journals, and citations via the Crossref API, and resolving DOIs to canonical metadata with authors, references, and citation graphs.332 npmMIT
- AlicenseAqualityDmaintenanceEnables retrieval of academic literature metadata via DOI or search using the Crossref REST API.2MIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude and other MCP-compatible clients to query Semantic Scholar and Crossref for scholarly works, retrieving metadata, abstracts, TL;DR summaries, and full-text links when available.-
- FlicenseNot gradedqualityAmaintenanceEnables Claude and other MCP-compatible clients to search for academic papers and retrieve metadata, abstracts, and full-text content from Semantic Scholar and Crossref through structured tool responses.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs such as Claude to search and retrieve academic paper information from Semantic Scholar and Crossref, including metadata, abstracts, full-text content when available, and topic/date-filtered results.-
TDQS
Scored across 18 tools
Each tool targets a distinct entity (member, journal, funder, type, license, prefix, work). The only confusion is get_work_quality, which sounds like a quality metric but actually queries a DOI's registration agency; the description clarifies, but the name could mislead.
Most tools follow a clear verb_noun pattern (search_*, get_*, list_*), with consistent entity-specific suffixes like '_works'. The outlier is get_work_quality, which uses a non-entity noun and doesn't reflect its purpose; ping is also non-standard but acceptable.
At 18 tools, this is slightly above the ideal 3-15 range, but the broad scope of Crossref's API—covering multiple entity types plus complex work search—justifies the count. No tool feels redundant or extraneous.
The set covers search and retrieval for members, journals, funders, works, types, licenses, and prefixes, including references. However, there is no endpoint for works citing a given DOI (forward citations), which is a notable gap for a scholarly metadata server.