Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.bakhtiersizhaev/openevidence-mcp

NPM · OPENEVIDENCE-MCP · SCANNED AUG 3

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

Available components

+19 this week 66 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (98 of 102), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (98 of 102), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 802 tokens (~160/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · openevidence-mcp

# add to Claude Code
claude mcp add bakhtiersizhaev-openevidence-mcp -- npx -y openevidence-mcp
# add to Codex CLI
codex mcp add bakhtiersizhaev-openevidence-mcp -- npx -y openevidence-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bakhtiersizhaev-openevidence-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "openevidence-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bakhtiersizhaev-openevidence-mcp --command npx --arg -y --arg openevidence-mcp
# ~/.hermes/config.yaml
mcp_servers:
  bakhtiersizhaev-openevidence-mcp:
    command: "npx"
    args: ["-y", "openevidence-mcp"]
// mcp.json
{
  "mcpServers": {
    "bakhtiersizhaev-openevidence-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "openevidence-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +59
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Dependency health: partial → unverified functional
    • Security disclosure: fail → unverified functional
    • Tool coverage: unverified → 100 functional
    • License: unverified → pass functional
    • Schema quality: unverified → 100 functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Schema quality: unverified → good functional
    • Licence: Apache-2.0 functional
  • 1 Aug 26 −22
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 47

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 98 packages

98 packages in the resolved dependency tree · 96 deprecated · 30 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~585 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
oe_article_get ~96

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.

NameTypeReqDescription
article_idstringyes
include_rawboolean

No output schema declared.

No examples provided.

oe_article_wait ~127

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. Requires authenticated session. No side effects.

NameTypeReqDescription
article_idstringyes
include_rawboolean
poll_interval_msinteger
timeout_secinteger

No output schema declared.

No examples provided.

oe_ask ~170

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: creates a question/article in the user's OpenEvidence account through the local browser profile.

NameTypeReqDescription
article_typestring
disable_cachingboolean
original_article_idstring
personalization_enabledboolean
poll_interval_msinteger
questionstringyes
timeout_secinteger
variant_configuration_filestring
wait_for_completionboolean

No output schema declared.

No examples provided.

oe_auth_status ~77

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

oe_history_list ~115

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 side effects.

NameTypeReqDescription
include_rawboolean
limitinteger
offsetinteger
searchstring

No output schema declared.

No examples provided.