Openevidence MCP server

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

• 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 43 days ago12/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

88/100

higher than 70% of 875 Scraping and browsing servers

Tools

5

the typical Scraping and browsing server has 7

Tools that change things

20%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

49

more than 89% of 595 Scraping and browsing servers

Downloads a week

68

more than 38% of 355 Scraping and browsing servers with a package

Openevidence: common questions

Is Openevidence MCP server safe?

Yes, by our scan: it is graded A (88/100). Read the Openevidence safety report

How do I install Openevidence?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop 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 51 days ago (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: Actionbook MCP server, Slack MCP Server and Zenrows MCP server. Compare all Openevidence alternatives.

How does Openevidence compare with other Scraping and browsing MCP servers?

safety score 88/100 (higher than 70% of 875 Scraping and browsing servers); tools 5 (the typical Scraping and browsing server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.