Skip to main content
Glama

Related Servers

Alternatives to UniArticles MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Unifies nine upstream paper-search servers behind one endpoint, letting an agent search 40+ academic sources, fetch full texts, trace citation graphs, pull peer-review data, and run an end-to-end research pipeline. It auto-detects identifiers like arXiv IDs and DOIs, fans queries out across backends in parallel, and works without any credentials.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to search academic literature across multiple sources (IEEE, arXiv, ACM, Semantic Scholar, CORE, Scite, Consensus) and index/search local PDFs.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to conduct literature reviews by screening multiple academic databases, performing backward and forward citation snowballing, and resolving or downloading full-text PDFs through subscription and open-access sources.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to search and analyze academic papers from multiple sources, fetch metadata and full text, and build structured outputs like literature maps and paper comparisons.
      73 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to search, analyze, and summarize academic research papers in real-time from arXiv, Semantic Scholar, and PubMed. Provides automatic deduplication, citation analysis, and BibTeX generation across multiple research databases.
      82 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search scholarly literature across Semantic Scholar, OpenAlex, arXiv, OpenReview, and CORE through one compact, rate-limit-aware interface, merging and de-duplicating results into a single list.
      MIT

    TDQS

    A3.6/5.0

    Scored across 29 tools

    Disambiguation4/5

    The tools are largely distinct by their target source (Scopus, PubMed, arXiv, etc.). However, there is some potential confusion between tools like 'core_work_search_by_query' and 'core_output_search_by_query' or 'pubmed_paper_search_by_query' vs 'europepmc_paper_search_by_query' if an agent doesn't read carefully, but descriptions clarify the differences.

    Naming Consistency4/5

    Most tool names follow a clear pattern of '<source>_<action>_<object>_by_<identifier>' (e.g., scopus_document_search_by_query, arxiv_paper_detail_by_id). Deviations exist like 'arxiv_latest_paper_list_by_category' and 'scopus_api_usage_status' which break the pattern slightly, but overall it is consistent and readable.

    Tool Count3/5

    With 29 tools, the count is on the high side but not extreme. The server aggregates multiple scholarly APIs (Scopus, arXiv, PubMed, Crossref, CORE, etc.), so many tools are needed. However, it feels slightly heavy and could be streamlined (e.g., combining some CORE output tools).

    Completeness4/5

    The domain is scholarly literature search and retrieval across multiple sources. Each source has at least a search and detail tool, covering core workflows. Minor gaps: no update or delete operations (not applicable for read-only APIs), but missing citation or full-text retrieval for some sources (e.g., no direct arXiv full-text download, no PubMed Central full-text retrieval beyond linkage).

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues