Evipedia
NPM · EVIPEDIA-MCP · SCANNED SEP 30
MCP Server for evipedia.ai — evidence-based reviews of health & longevity interventions
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
- 32 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1760 tokens (~220/item across 8 items; 8 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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 Evipedia MCP server?
Evipedia runs locally as an npm package, launched with npx -y evipedia-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 · evipedia-mcp
claude mcp add forever-healthy-evipedia-mcp -- npx -y evipedia-mcp
{
"mcpServers": {
"forever-healthy-evipedia-mcp": {
"command": "npx",
"args": [
"-y",
"evipedia-mcp"
]
}
}
} {
"servers": {
"forever-healthy-evipedia-mcp": {
"command": "npx",
"args": [
"-y",
"evipedia-mcp"
]
}
}
} codex mcp add forever-healthy-evipedia-mcp -- npx -y evipedia-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"forever-healthy-evipedia-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"evipedia-mcp"
],
"enabled": true
}
}
} openclaw mcp add forever-healthy-evipedia-mcp --command npx --arg -y --arg evipedia-mcp
mcp_servers:
forever-healthy-evipedia-mcp:
command: "npx"
args: ["-y", "evipedia-mcp"] {
"McpServers": {
"forever-healthy-evipedia-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"evipedia-mcp"
]
}
}
} assistant mcp add forever-healthy-evipedia-mcp -t stdio -c npx -a -y evipedia-mcp
{
"mcpServers": {
"forever-healthy-evipedia-mcp": {
"command": "npx",
"args": [
"-y",
"evipedia-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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −1
- Stability: fail → 0.83 functional
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 30 Sept 2026 · Analysed npm/evipedia-mcp@0.1.30
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 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 32 |
| 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 →
get_conclusion ~150
Get just the plain-text conclusion of an evidence review — the evidence-based bottom line, without the methodology, findings, or references. Prefer this for 'does X work?' questions; use get_review only when the user needs the full evidence, or get_metadata for dates and citations. Takes a slug from search_reviews, list_reviews, or list_updates; a full https://evipedia.ai/{slug} URL is also accepted and normalised to the slug. Read-only, no authentication required; an unknown slug raises "Review not found: {slug}".
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Review slug, e.g. 'rapamycin' (a full evipedia.ai URL is also accepted) |
No output schema declared.
No examples provided.
get_metadata ~125
Get a review's structured medical metadata as JSON: review dates (datePublished/dateModified/lastReviewed — a freshness signal absent from the Markdown), the intervention as a typed `about` entity with alternate names, and an ordered `citation` list of primary sources (each with a PubMed `pmid` when available). Use when you need the review's freshness, machine-readable references/PMIDs, or drug classification rather than prose.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Review slug, e.g. 'rapamycin' (a full evipedia.ai URL is also accepted) |
No output schema declared.
No examples provided.
get_review ~145
Get the full evidence review as raw Markdown — methodology, findings, safety, dosing, and references. Reviews are long (often 10k+ tokens); use get_conclusion when the bottom line is enough, or get_metadata for machine-readable dates and citations. Takes a slug from search_reviews, list_reviews, or list_updates; a full https://evipedia.ai/{slug} URL is also accepted and normalised to the slug. Read-only, no authentication required; an unknown slug raises "Review not found: {slug}".
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Review slug, e.g. 'rapamycin' (a full evipedia.ai URL is also accepted) |
No output schema declared.
No examples provided.
get_version ~30
Get the running evipedia MCP server's package name and version. Useful to confirm which build is loaded.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_reviews ~155
List every evidence review in the evipedia.ai catalogue. Returns a JSON array of {topic, slug}, where topic is the review's canonical topic and slug is its identifier. Pass a slug directly to get_review or get_conclusion; the full review URL is https://evipedia.ai/{slug} (raw Markdown at https://evipedia.ai/{slug}.md). A bare topic (just the intervention name, e.g. 'Rapamycin') implies the default Health & Longevity goal; a topic with an explicit goal (e.g. 'Botox for Skin Rejuvenation') is a review targeting that specific goal. Use to enumerate or browse the full catalogue; use search_reviews to find specific reviews.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_updates ~233
List recently published or revised evipedia.ai reviews, newest first — the catalogue's change feed. Returns a JSON array of {title, slug, status, date}, where status is 'new' (first publication) or 'updated' (an existing review revised) and date is YYYY-MM-DD. Called with no arguments it returns the last 7 days, capped at the 100 most recent entries; pass `days` for a different window (e.g. days: 30) — an explicit `days` is never capped, so a wide window can return hundreds of entries. The full review is at https://evipedia.ai/{slug}, and get_conclusion/get_review take the slug. Use this for recency ('what's new?'); use list_reviews to enumerate the whole catalogue and search_reviews to find a specific intervention.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Only include reviews dated on or after (today − N days), e.g. 7 for the past week. Omit to use the default 7-day window. The catalogue turns over quickly — a large window returns hundreds of entries. |
No output schema declared.
No examples provided.
search_reviews ~95
Search evipedia.ai evidence reviews by name, synonym, keyword, or category. A discovery tool: returns the matching reviews (goal-qualified topic + URL) ranked by relevance so you can tell whether a review exists. To read one, pass its slug to get_conclusion (quick bottom line) or get_review (full Markdown).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query — intervention name, synonym, drug class, or category |
No output schema declared.
No examples provided.
suggest_review ~216
Suggest a new review for evipedia.ai — propose an intervention the catalogue doesn't cover yet. Submits to evipedia's public suggestion form (the same one at evipedia.ai/suggest). Use only when the user explicitly wants to propose a new review — this sends a message to the evipedia team. Search first with search_reviews to confirm the catalogue doesn't already cover it. Only `intervention` is required; `goal`, `references`, and `email` are optional and are forwarded verbatim. Returns a plain-text confirmation on success and raises "Suggestion failed: HTTP {status}" otherwise. Not idempotent — calling it twice files two separate suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Optional submitter email, so the evipedia team can follow up | |
| goal | string | – | Optional health or longevity goal the intervention targets |
| intervention | string | yes | Name of the intervention to suggest (e.g. 'Urolithin A') |
| references | string | – | Optional supporting references or links |
No output schema declared.
No examples provided.
What is the Evipedia MCP server?
Evipedia is an MCP server listed in the public MCP registry as io.github.forever-healthy/evipedia-mcp. MCP Server for evipedia.ai, evidence-based reviews of health & longevity interventions. This page covers its npm package (evipedia-mcp).
Is the Evipedia MCP server safe to use?
Evipedia scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 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 Evipedia MCP server expose?
Evipedia exposes 8 tools: search_reviews, list_reviews, list_updates, get_conclusion, get_review, and 3 more. Their descriptions and schemas cost roughly 1,149 tokens of context every time the server is loaded.
Is the Evipedia MCP server still maintained?
Evipedia is still listed as active in the MCP registry. We last reached this channel on 30 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 Evipedia MCP server under?
Evipedia declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.