Mmcp.market

Openevidence MCP server

by bakhtiersizhaev·io.github.bakhtiersizhaev/openevidence-mcp·v0.2.2

Unofficial MCP server connecting OpenEvidence to AI agents via authenticated browser sessions

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

41 stars58 downloads/wk

Reviews

Write one

Nobody has reviewed Openevidence yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Openevidence tools (5, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • oe_article_get

    Fetch an OpenEvidence article by article_id. Use after history lookup or oe_ask returns an article ID. Inputs: article_id UUID, optional include_raw=false. Returns normalized status, question, and answer fields by default. include_raw=true may expose private thread context and must be used only with explicit user intent. Requires authenticated session. No side effects.

  • oe_article_wait

    Wait for an existing OpenEvidence article_id to finish, then return normalized fields. Use after oe_ask with wait_for_completion=false, especially for long research questions that may exceed MCP host timeouts. Inputs: article_id UUID, optional timeout_sec, poll_interval_ms, and include_raw=false. include_raw=true may expose private thread context and must be used only with explicit user intent. Re

  • oe_askwrite action

    Create an OpenEvidence research question, not medical advice or patient-specific diagnosis. For long questions, prefer wait_for_completion=false and then call oe_article_wait with the returned article_id. Use original_article_id only for true follow-up continuity; omit it for fresh questions. Returns privacy-reduced created article data and optionally normalized completed fields. Side effect: crea

  • oe_auth_status

    Check whether the saved OpenEvidence browser session is authenticated. Use before history/article/ask tools when auth state is unknown. Returns authenticated=true/false and basic account metadata when available. Requires the local browser profile created by npm run login:session. No side effects. Can fail if the profile is missing, expired, or network access fails.

  • oe_history_list

    List prior OpenEvidence articles from the authenticated account. Use only when the user asks to inspect prior OpenEvidence work or needs an article_id. Inputs: limit, offset, optional search, optional include_raw=false. Returns a privacy-reduced list by default; include_raw=true may expose private prior questions and must be used only with explicit user intent. Requires authenticated session. No s

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan17 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Openevidence repository's README, as published. We do not edit it. Read it on GitHub

OpenEvidence MCP (Unofficial)

No API key is required. Authenticate once with npm run login:session; the server reuses your local browser profile. Registry metadata version 0.2.2 continues to use the existing npm package 0.2.1.

OpenEvidence MCP is an unofficial Model Context Protocol server that connects OpenEvidence to Codex, Claude Code, Claude Desktop, Cursor, Cline, Continue, and other MCP-compatible clients through your own authenticated browser session.

[!IMPORTANT]

This project is unofficial and is not affiliated with OpenEvidence. It does not provide medical advice, does not bypass access controls, and should only be used with your own OpenEvidence account in compliance with applicable terms, privacy rules, and clinical governance requirements.

Translations: Русский | Español | 简体中文 | 繁體中文(台灣) | 한국어 | हिन्दी

Agent Onboarding & Installation

Using Codex, Claude Code, Cursor, or another local AI coding agent? You can let the agent handle the entire setup, compilation, and local MCP configuration for you!

Copy and paste this short bootstrap prompt directly into your local AI coding assistant:

Please install OpenEvidence MCP for me: clone https://github.com/bakhtiersizhaev/openevidence-mcp, install dependencies, run build, auto-configure this MCP server in my local client (Claude Desktop/Codex/Cursor), guide me through the one-time Edge/Chrome login using `npm run login:session`, and run `npm run smoke` to verify. Keep everything strictly local and secure.

For the comprehensive, step-by-step setup playbook and rules, see docs/AGENTINSTALLPROMPT.md.

What it does

OpenEvidence MCP runs a local stdio MCP server that lets MCP clients use your existing OpenEvidence browser session for:

  • checking whether the saved session is authenticated;
  • listing your OpenEvidence question/article history;
  • fetching a full article payload by ID;
  • asking an OpenEvidence research question and optionally waiting for completion;
  • polling an existing OpenEvidence article until it completes.

No official OpenEvidence API token is required.

What it does NOT do

  • It is not affiliated with, endorsed by, or approved by OpenEvidence.
  • It does not provide medical advice or replace clinical judgment.
  • It does not bypass authentication, paywalls, or access controls.
  • It does not collect credentials.
  • It does not send your browser session state anywhere except to OpenEvidence through local requests from your machine.
  • It should not be used for patient-specific diagnosis or treatment decisions without appropriate human review.

Who it is for

  • clinicians using their own OpenEvidence account;
  • medical researchers;
  • AI operators building evidence-research workflows;
  • MCP developers integrating local tools with Codex, Claude, Cursor, Cline, Continue, or similar clients.

Tested / Target Clients

This project is designed for MCP-compatible clients and local agent workflows. Only Codex and Claude-style local configuration examples are maintained in this repository unless otherwise noted.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y openevidence-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add openevidence-mcp -- npx -y openevidence-mcp
Add to Cursor

Openevidence: common questions

Is Openevidence MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Openevidence safety report
How do I install Openevidence?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Openevidence need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Openevidence maintained?
The last commit was in the last day (2026-09-25). The latest release is v0.2.2.
What can I use instead of Openevidence?
Servers from other publishers that do the same job: Slack MCP Server, Zenrows MCP server and Aginx Browser MCP server. Compare all Openevidence alternatives.

Alternatives to Openevidence

Same job from other publishers: the closest match first, then the best rated.

All Openevidence alternatives →
  • Slack MCP Server
    Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth.
    A
  • Zenrows
    Zenrows MCP server — Fetch, Extract, Batch, and Browser Sessions for AI coding assistants
    A
  • Aginx Browser
    Stealth web browser for agents: search, fetch, click, download and type in persistent MCP sessions.
    B
  • Browserbase
    Browserbase MCP server: cloud browser sessions, agents, contexts, fetch, search, functions
    A
  • MCP Browser
    Browser automation using the user's Chromium session — JS execution, auth, and anti-bot support.
    B

More from bakhtiersizhaev →