Skip to main content
Glama
Sign In
preprint-fulltext

preprint-fulltext

by genecell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to preprint-fulltext

No user-submitted related servers found.

    Related Servers

    • rxiv

      sakzgupzzz
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude or any MCP client to search and read arXiv, bioRxiv, and medRxiv preprints, including metadata, paged full text, recent listings, and journal-publication checks.
      7
      MIT

    • 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.
      135 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.
      5 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.
      -
    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

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: full-text retrieval, metadata/abstract retrieval, identifier resolution, and search. The boundaries between get_fulltext and get_metadata are especially clear despite both taking a DOI, since one returns sections and the other returns bibliographic metadata.

    Naming Consistency4/5

    Names are consistently snake_case with a verb_noun pattern (get_fulltext, get_metadata, search_preprints). The bare verb 'resolve' is a minor deviation but remains readable and idiomatic for identifier resolution.

    Tool Count5/5

    Four tools is well-scoped for a focused preprint full-text server, with each tool covering a necessary operation: search, resolve, metadata, and full text. There is no redundant or filler tool.

    Completeness4/5

    The core lifecycle is covered: search, identifier resolution, metadata, and structured full-text retrieval, including version selection. Minor gaps remain, such as listing available versions or batch operations, but agents can work around them via resolve and get_fulltext.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources