medRxiv MCP Server

Created By
JackKuo666a year ago
Overview

What is medRxiv MCP Server?

The medRxiv MCP Server is a tool that enables AI assistants to search and access medRxiv papers through a simple Model Context Protocol (MCP) interface, facilitating access to health sciences preprints.

How to use medRxiv MCP Server?

To use the medRxiv MCP Server, install it via Smithery or manually, then start the server and configure it with your AI assistant to enable paper searches and access.

Key features of medRxiv MCP Server?

  • Paper Search: Custom queries to find medRxiv papers.
  • Efficient Retrieval: Quick access to paper metadata.
  • Paper Access: Download and read paper content.
  • Local Storage: Save papers for faster access.
  • Research Prompts: Specialized prompts for paper analysis.

Use cases of medRxiv MCP Server?

  1. Searching for recent health sciences research papers.
  2. Accessing detailed information about specific papers using DOI.
  3. Analyzing academic papers with specialized prompts.

FAQ from medRxiv MCP Server?

  • Can I search for any health sciences paper?

Yes, you can search for any paper available on medRxiv using custom queries.

  • Is there a specific Python version required?

Yes, Python 3.10 or higher is required to run the server.

  • How do I contribute to the project?

Contributions are welcome! You can submit a Pull Request on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JackKuo666
Star
1
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago