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
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 hours ago