io.github.bakhtiersizhaev/openevidence-mcp
NPM · OPENEVIDENCE-MCP · SCANNED SEP 20
Unofficial MCP server connecting OpenEvidence to AI agents via authenticated browser sessions
Available components
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 104 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- 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 Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.bakhtiersizhaev/openevidence-mcp server?
io.github.bakhtiersizhaev/openevidence-mcp runs locally as an npm package, launched with npx -y openevidence-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · openevidence-mcp
claude mcp add bakhtiersizhaev-openevidence-mcp -- npx -y openevidence-mcp
{
"mcpServers": {
"bakhtiersizhaev-openevidence-mcp": {
"command": "npx",
"args": [
"-y",
"openevidence-mcp"
]
}
}
} {
"servers": {
"bakhtiersizhaev-openevidence-mcp": {
"command": "npx",
"args": [
"-y",
"openevidence-mcp"
]
}
}
} codex mcp add bakhtiersizhaev-openevidence-mcp -- npx -y openevidence-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bakhtiersizhaev-openevidence-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"openevidence-mcp"
],
"enabled": true
}
}
} openclaw mcp add bakhtiersizhaev-openevidence-mcp --command npx --arg -y --arg openevidence-mcp
mcp_servers:
bakhtiersizhaev-openevidence-mcp:
command: "npx"
args: ["-y", "openevidence-mcp"] {
"McpServers": {
"bakhtiersizhaev-openevidence-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"openevidence-mcp"
]
}
}
} assistant mcp add bakhtiersizhaev-openevidence-mcp -t stdio -c npx -a -y openevidence-mcp
{
"mcpServers": {
"bakhtiersizhaev-openevidence-mcp": {
"command": "npx",
"args": [
"-y",
"openevidence-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/openevidence-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
oe_article_get OpenEvidence 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.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | string | yes | – |
| include_raw | boolean | – | – |
No output schema declared.
No examples provided.
oe_article_wait OpenEvidence 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.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | string | yes | – |
| include_raw | boolean | – | – |
| poll_interval_ms | integer | – | – |
| timeout_sec | integer | – | – |
No output schema declared.
No examples provided.
oe_ask OpenEvidence 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.
| Name | Type | Req | Description |
|---|---|---|---|
| article_type | string | – | – |
| disable_caching | boolean | – | – |
| original_article_id | string | – | – |
| personalization_enabled | boolean | – | – |
| poll_interval_ms | integer | – | – |
| question | string | yes | – |
| timeout_sec | integer | – | – |
| variant_configuration_file | string | – | – |
| wait_for_completion | boolean | – | – |
No output schema declared.
No examples provided.
oe_auth_status OpenEvidence 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 OpenEvidence 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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_raw | boolean | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| search | string | – | – |
No output schema declared.
No examples provided.
What is the io.github.bakhtiersizhaev/openevidence-mcp server?
io.github.bakhtiersizhaev/openevidence-mcp is listed in the public MCP registry as io.github.bakhtiersizhaev/openevidence-mcp. Unofficial MCP server connecting OpenEvidence to AI agents via authenticated browser sessions. This page covers its npm package (openevidence-mcp).
Is the io.github.bakhtiersizhaev/openevidence-mcp server safe to use?
io.github.bakhtiersizhaev/openevidence-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.bakhtiersizhaev/openevidence-mcp server expose?
io.github.bakhtiersizhaev/openevidence-mcp exposes 5 tools: oe_auth_status, oe_history_list, oe_article_get, oe_article_wait, oe_ask. Their descriptions and schemas cost roughly 585 tokens of context every time the server is loaded.
Is the io.github.bakhtiersizhaev/openevidence-mcp server still maintained?
io.github.bakhtiersizhaev/openevidence-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.bakhtiersizhaev/openevidence-mcp server under?
io.github.bakhtiersizhaev/openevidence-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.