Evipedia
NPM · EVIPEDIA-MCP · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (96 of 100), 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 (96 of 100), so this covers what we could see, not the whole tree. 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 17 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 1166 tokens (~166/item across 7 items; 7 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 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · evipedia-mcp
claude mcp add forever-healthy-evipedia-mcp -- npx -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": {
"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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +45
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 44
First indexed and scored.
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 96 packages
96 packages in the resolved dependency tree · 96 deprecated · 30 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
get_conclusion ~49
Get just the plain-text conclusion of an evidence review.
| 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 ~46
Get the full evidence review as raw Markdown.
| 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.
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_intervention ~138
Suggest a new intervention for evipedia.ai to review. 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 intervention — this sends a message to the evipedia team.
| 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.