Skip to main content
Glama
Sign In
paper-fetch-mcp

paper-fetch-mcp

by Dictation354
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to paper-fetch-mcp

No user-submitted related servers found.

    Related Servers

    • paper-search-mcp

      morosss
      A
      license
      Not graded
      quality
      D
      maintenance
      A MCP server for searching and downloading academic papers from arXiv, PubMed, bioRxiv, and more. It integrates with LLMs like Claude Desktop for paper discovery.
      MIT

    • dbv-pdf2md

      davidbuenov
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that converts PDFs to Markdown, reconstructing hidden hyperlinks and extracting images in reading order for AI agents.
      MIT

    • ScholarMCP

      lstudlo
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables coding agents to search academic papers, ingest full-text PDFs, extract structured details, and manage citations in literature research workflows.
      32
      MIT

    • Scholar MCP Server

      mlintangmz2765
      A
      license
      A
      quality
      D
      maintenance
      Unified MCP server for scientific literature search and extraction, integrating databases like Scopus, OpenAlex, Semantic Scholar, and Unpaywall to enable AI agents to discover papers, track citations, and analyze content.
      27
      MIT

    • Paper Search MCP

      openags
      A
      license
      B
      quality
      B
      maintenance
      An MCP server for searching and downloading academic papers from multiple sources including arXiv, PubMed, bioRxiv, and Sci-Hub, designed for seamless integration with large language models like Claude Desktop.
      57
      3,497 PyPI
      3,009
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tools fall into clear functional groups: single/batch resolve (resolve_paper/batch_resolve), single/batch fetch (fetch_paper/batch_fetch), cache reads (list_cached/get_cached), and diagnostics (provider_status/browser_preflight). The singular-vs-batch and static-vs-live distinctions are stated explicitly, though the cache pair (list_cached vs get_cached) and batch_check vs fetch boundaries require careful reading of very dense descriptions to separate.

    Naming Consistency3/5

    Casing is uniformly snake_case, but the verb-first convention is broken: batch_check, batch_fetch, and batch_resolve lead with a modifier rather than a verb, and provider_status/browser_preflight are noun-noun. The batch_ prefix is systematic and readable, but the set mixes several structural patterns rather than one predictable verb_noun form.

    Tool Count5/5

    Nine tools is well-scoped for a paper-fetch server, with each tool earning its place across resolve, fetch, cache, and diagnostics concerns. Single and batch variants are paired cleanly without redundancy.

    Completeness4/5

    The core lifecycle—resolve, probe/check, fetch, and cache inspection—is fully covered for both single and batch workflows, plus diagnostics for providers and the browser path. The main gap is cache management: there is no way to clear or delete cached entries, only to list and look them up.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources