Skip to main content
Glama

Related Servers

Alternatives to eprintdl

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      D
      maintenance
      Enables academic research through paper search across multiple databases (IACR, CryptoBib, Crossref, Google Scholar), PDF processing, and GitHub repository browsing. Features modular architecture with FastMCP-based proxy server routing to specialized academic tools.
      7
      51 PyPI
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude Code and Codex to drive a local literature-retrieval workflow: import DOIs or references, find and download legal open-access full texts first, submit requests through the user's own personal account when needed, and monitor or verify the resulting PDFs.
      AGPL 3.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Desktop, Claude Code, and Cursor to access and process arXiv papers by fetching their LaTeX source, with tools for full paper prompts, abstracts, section listings, and specific sections. This allows accurate interpretation of mathematical expressions and notation in equation-heavy papers.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude to search over 450,000+ open-access papers, standards, and legal documents, download PDFs, retrieve citations, and fetch full document metadata.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Desktop, Claude Code, and Cursor to directly access and process scientific papers by retrieving and flattening their LaTeX sources. It provides tools for full paper prompts, abstracts, section headings, and specific sections, improving handling of equations and mathematical notation.
      -

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a clearly different stage of the pipeline: metadata lookup (search), fetching PDFs (download), library/config state (status), and file integrity checks (verify). There is no meaningful overlap — an agent can pick the right tool from the name alone, and the descriptions reinforce the boundaries.

    Naming Consistency5/5

    All four tools share the same `eprint_` prefix followed by a single lowercase verb/noun in snake_case: search, download, status, verify. The pattern is uniform and predictable; the only mild variation is `status` being a noun rather than a verb, which is idiomatic and unambiguous.

    Tool Count4/5

    Four tools is well-scoped for a focused eprint downloader and each one earns its place without redundancy. However, the surface is thin enough that a missing operation (e.g. harvest/refresh) pushes the set just past the ideal for its scope.

    Completeness3/5

    Search/download/status/verify cover the core fetch-and-check loop, but `eprint_search` explicitly instructs the agent to call a `harvest` tool that is not exposed, creating a documented dead end when a year is missing from the local DB. Configuration/credential refresh is also only implied via download's Cloudflare note, so the lifecycle is not fully closed.