4,000+ servers built on vurb.ts
Vinkius
CursorIDE
Stanford bioRxiv MCP Server

Bring Biorxiv
to Cursor

Learn how to connect Stanford bioRxiv to Cursor and start using 16 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get PreprintGet Preprint VersionsGet Published TrackingGet Published VersionGet Recent BiorxivGet Recent MedrxivSearch BiorxivSearch By CategorySearch By InstitutionSearch CancerSearch Cell BiologySearch EpidemiologySearch GenomicsSearch ImmunologySearch MedrxivSearch Neuroscience

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Stanford bioRxiv

What is the Stanford bioRxiv MCP Server?

Connect to the bioRxiv and medRxiv APIs — the world's leading preprint servers for biology and health sciences.

What you can do

  • bioRxiv Preprints — Browse the latest biology preprints across 25+ categories
  • medRxiv Preprints — Browse health sciences preprints (clinical, epidemiology, public health)
  • Category Filters — Neuroscience, genomics, cell biology, cancer, immunology, and more
  • Preprint Details — Get full metadata including abstracts by DOI
  • Version Tracking — See how a preprint has been revised over time
  • Publication Tracking — Discover which preprints have been published in peer-reviewed journals
  • Institution View — Browse preprints by corresponding author institution
  • Subject Feeds — Dedicated feeds for neuroscience, genomics, immunology, cell biology, cancer, and epidemiology

Why preprints matter

Preprints appear 6-12 months before peer-reviewed publication. This server gives you access to science at the cutting edge — the same day researchers share their findings with the world.

Who is this for?

  • Biologists — stay current with your field before journals publish
  • Medical Researchers — monitor clinical and epidemiological preprints
  • PhD Students — discover the freshest research in your specialty
  • Science Journalists — track breaking scientific discoveries

Built-in capabilities (16)

get_preprint

Searches both bioRxiv and medRxiv. Returns title, authors, corresponding author and institution, date, version, category, abstract, and license. DOI format: "10.1101/2024.01.15.575123". Get preprint details by DOI

get_preprint_versions

Preprints on bioRxiv/medRxiv can be updated multiple times. This lets you see the full revision history and understand how a manuscript has evolved. Get all versions of a preprint to track revisions

get_published_tracking

Shows the preprint DOI, published DOI, journal name, and publication date. Essential for understanding the preprint-to-publication pipeline. Track which preprints have been published in journals

get_published_version

Returns the published DOI, journal citation, and publication date. Essential for finding the final, peer-reviewed version of a preprint you have read. Find the journal-published version of a preprint

get_recent_biorxiv

Default is 7 days. Essential for staying at the cutting edge of biological research — preprints appear here 6-12 months before peer-reviewed publication. Get the latest bioRxiv preprints

get_recent_medrxiv

Covers clinical medicine, epidemiology, public health, and health systems research. Critical for monitoring emerging health research before journal publication. Get the latest medRxiv preprints

search_biorxiv

The bioRxiv API returns preprints in batches of 100. Use the date interval format "YYYY-MM-DD/YYYY-MM-DD" (e.g. "2024-01-01/2024-01-31"). Use cursor for pagination (0, 100, 200, etc.). Browse bioRxiv preprints by date range

search_by_category

bioRxiv categories include: neuroscience, genomics, bioinformatics, cell_biology, cancer_biology, immunology, microbiology, molecular_biology, biochemistry, genetics, developmental_biology, evolutionary_biology, ecology, plant_biology, physiology, pharmacology, systems_biology, biophysics, synthetic_biology. medRxiv categories: epidemiology, infectious_diseases, public_and_global_health, health_systems, cardiovascular_medicine, oncology, psychiatry, neurology. Filter preprints by subject category

search_by_institution

Use this to explore what institutions are producing preprints in a given time period. Each preprint includes the corresponding author and their institutional affiliation. Browse preprints with author institution metadata

search_cancer

Covers tumor biology, oncogenomics, cancer immunology, drug resistance, and experimental therapeutics. Browse cancer biology preprints

search_cell_biology

Covers cell signaling, organelle biology, cytoskeleton, cell division, stem cells, and cellular mechanisms of disease. Browse cell biology preprints

search_epidemiology

Covers disease surveillance, outbreak analysis, population health, health policy, and clinical epidemiology. Critical for public health monitoring. Browse epidemiology and public health preprints

search_genomics

Covers genome sequencing, gene regulation, epigenomics, metagenomics, and computational genomics — core disciplines in modern biology. Browse genomics and bioinformatics preprints

search_immunology

Covers immune system research, host-pathogen interactions, vaccine development, autoimmune diseases, and immunotherapy. Browse immunology and microbiology preprints

search_medrxiv

medRxiv covers clinical research, epidemiology, public health, and health policy. Use interval "YYYY-MM-DD/YYYY-MM-DD" format. Results paginated in batches of 100. Browse medRxiv preprints by date range

search_neuroscience

Neuroscience is one of the largest and most active categories, covering brain research, neural circuits, cognitive science, and neurological disorders. Browse neuroscience preprints

Why Cursor?

Cursor's Agent mode turns Stanford bioRxiv into an in-editor superpower. Ask Cursor to generate code using live data from Stanford bioRxiv and it fetches, processes, and writes. all in a single agentic loop. 16 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

  • Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

  • Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

  • MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

  • VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

Stanford bioRxiv in Cursor

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Stanford bioRxiv and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Stanford bioRxiv to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Stanford bioRxiv in Cursor

The Stanford bioRxiv MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 16 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Stanford bioRxiv
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Stanford bioRxiv for Cursor

Every tool call from Cursor to the Stanford bioRxiv MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Do I need an API key?

No. The bioRxiv and medRxiv APIs are completely free and public.

02

What is the difference between bioRxiv and medRxiv?

bioRxiv covers biological sciences (neuroscience, genomics, cell biology, ecology, etc.) while medRxiv covers health sciences (clinical research, epidemiology, public health, health systems).

03

Are preprints peer-reviewed?

No. Preprints are shared before formal peer review. They undergo basic screening but not the full editorial process. This server also tracks which preprints later get published in peer-reviewed journals.

04

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

05

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

06

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

07

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

08

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

09

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Explore More MCP Servers

View all →