easyscholar-mcp
Related Servers
Alternatives to easyscholar-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables MCP-capable AI clients to query journal evaluation data such as CAS partitions, JCR impact factors and quartiles, XinRui partitions, CCF recommended catalogs, and international warning lists, plus aggregate a full checkup of a journal across all sources. Also supports reverse journal recommendation from paper topic keywords and fuzzy journal name or ISSN lookup.1-
- AlicenseNot gradedqualityCmaintenanceProvides access to journal partition tables, impact factors, and warning lists from Chinese Academy of Sciences and JCR databases. Enables searching, comparing journals, analyzing partition trends, and checking journal warning status across multiple years.9MIT
- AlicenseAqualityDmaintenanceEnables multi-source literature search, full-text retrieval, reference analysis, and journal quality assessment across Europe PMC, PubMed, arXiv, CrossRef, OpenAlex, and EasyScholar via the MCP protocol.522 npm1MIT
- AlicenseAqualityDmaintenanceProvides access to the Elsevier Scopus API, enabling AI assistants to search for academic papers, retrieve detailed abstracts, and look up author profiles. It facilitates bibliometric research and scholarly data analysis through natural language commands.5177 PyPI55MIT
- AlicenseAqualityDmaintenanceEnables streamlined academic research and author disambiguation by providing AI agents with optimized access to the OpenAlex.org API. It supports searching for authors, resolving institutional affiliations, and retrieving scholarly works with detailed citation metrics.857MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query the Semantic Scholar Academic Graph for scholarly paper data, supporting tools for search, retrieval, and analysis.73 npmMIT
TDQS
Scored across 2 tools
The two tools are clearly separated by cardinality: journal_rank handles one title, journal_ranks handles up to 50, and both descriptions state this explicitly. The singular/plural distinction is the only potential confusion point, but the descriptions make selection straightforward.
Both names follow the same noun-based pattern with a singular/plural pair (journal_rank / journal_ranks), which is predictable and readable. The only minor deviation is that neither uses a verb prefix like get_ or lookup_, so the action must be inferred from the noun.
The domain is deliberately narrow (journal metric lookup), so two tools are defensible, but it sits at the thin end where a single tool with a list parameter could have covered both cases. The batch tool does earn its place given the ~0.6s per-request throttle.
Core metric retrieval is well covered, including caching, spelling fallbacks, and rich metric keys. However, there is no way to search or discover journals by keyword, ISSN, or category, so an agent that doesn't already know the exact title has a dead end beyond the automatic respelling attempts.