Unofficial bioRxiv MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| biorxiv_infoB | Unified bioRxiv/medRxiv preprint database access. 260K+ preprints. Methods: search_preprints (keyword search with date range filtering), get_preprint_details (full metadata by DOI), get_categories (list subject categories), search_published_preprints (find preprints published in journals), search_by_funder (find preprints by funding org ROR ID), get_content_statistics (submission stats), get_usage_statistics (views/downloads stats). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with other tools. The tool's description clearly enumerates its methods, so an agent can understand its purpose without ambiguity.
The single tool name 'biorxiv_info' is clear and follows a consistent naming style. Since there are no other tools to contrast with, consistency is trivially high.
A single tool is borderline for a server, but given the narrow scope of bioRxiv/medRxiv access, it can be acceptable. However, it feels thin compared to servers that expose separate tools for distinct operations.
The tool bundles methods covering search, metadata retrieval, category listing, publication status, funder lookup, and statistics. This provides broad coverage of preprint database operations, with no obvious dead ends.