Skip to main content
Glama
genecell

preprint-fulltext

by genecell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to preprint-fulltext

No user-submitted related servers found.

    Related Servers

    • mcp-biorxiv

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying bioRxiv and medRxiv preprints, including metadata, publication status, and submission counts, through natural language or direct tool calls.
      21 npm
      MIT

    • @cyanheads/pubmed-mcp-server

      MihoSharma24958
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching PubMed and Europe PMC, fetching article metadata and full text via PMC, Europe PMC, or Unpaywall, resolving citations and identifiers, and looking up MeSH terms through MCP. Runs over STDIO or Streamable HTTP with 11 tools, 1 resource, and 1 prompt.
      9 npm
      MIT

    • arxiv-mcp

      aliildan
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching arXiv, fetching metadata, reading papers as section-aware Markdown, listing recent papers, and downloading PDFs via five MCP tools.
      22 npm
      2
      MIT

    • PaperPilot

      sharadvc
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search and retrieve academic papers from arXiv and PubMed with citation-grade extraction, providing clean citations and summaries.
      -

    • paper-search-mcp

      xiaoxiaoxiaotao
      F
      license
      A
      quality
      D
      maintenance
      Enables agents to search papers across Semantic Scholar and arXiv, read and extract text from arXiv PDFs, align records across sources, and produce structured literature-analysis digests.
      10
      1
      -
    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.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search_preprints for searching, get_fulltext for retrieving full text, get_metadata for bibliographic metadata, and resolve for ID conversion. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (search_preprints, get_fulltext, get_metadata). 'resolve' is a single verb but fits the pattern of concise, predictable naming.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its domain. Each tool serves a core function without being under- or over-provisioned, making it easy for agents to navigate.

    Completeness5/5

    The tool surface covers the essential operations for preprint fulltext retrieval: searching, full-text access, metadata retrieval, and ID resolution. There are no obvious gaps or dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources