# evipedia-mcp [Health: Active]

**Category:** 🧬 Biology & Bioinformatics  
**Repository:** https://github.com/forever-healthy/evipedia-mcp  
**GitHub Stars:** 2  
**npm Downloads (last month):** 290  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/evipedia-mcp

## Description
MCP Server for evipedia.ai — evidence-based reviews of health & longevity interventions

## Tools
Capabilities this server exposes over MCP:

- **search_reviews** — 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).
- **list_reviews** — 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.
- **list_updates** — 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.
- **get_conclusion** — 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}".
- **get_review** — 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}".
- **get_metadata** — 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.
- **suggest_review** — 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.
- **get_version** — Get the running evipedia MCP server's package name and version. Useful to confirm which build is loaded.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "evipedia-mcp": {
    "command": "npx",
    "args": ["-y","evipedia-mcp"]
  }
}
```

## Documentation

## What evipedia-mcp MCP server does

The evipedia-mcp MCP server connects AI agents to evipedia.ai's public evidence-review content. It is intended for retrieving information about health and longevity interventions, rather than querying a private content repository or a general medical database.

Read operations cover review discovery, complete review text, conclusions, metadata, and update history. The server also exposes a write operation for submitting a proposed intervention to evipedia's public suggestion form. A version tool reports the installed package name and version.

## How it works

The evipedia-mcp MCP server is a thin client that fetches data from public evipedia.ai endpoints. It does not require authentication for its read operations and does not depend on the evipedia content repository. A small in-process cache is used for the JSON indexes.

Review reads accept either a bare slug, such as `rapamycin`, or a complete evipedia.ai URL. When given a URL, the server uses its final path segment as the review slug. This allows an agent to pass a URL returned by search directly into a read operation.

The underlying endpoints provide a full catalogue, a search index, an update feed, raw Markdown reviews, flattened metadata, and supporting site feeds and indexes. The suggestion operation sends a POST request to evipedia's public Formspree-backed form.

## Setup and configuration

The package is published on npm and can run locally over stdio with Node.js 18 or newer. A local client can launch it without a global installation:

```json
{
  "mcpServers": {
    "evipedia": {
      "command": "npx",
      "args": ["-y", "evipedia-mcp"]
    }
  }
}
```

A hosted endpoint is also available at `https://mcp.evipedia.ai/mcp` for clients that support HTTP MCP connections:

```json
{
  "mcpServers": {
    "evipedia": {
      "type": "http",
      "url": "https://mcp.evipedia.ai/mcp"
    }
  }
}
```

No environment variables or authentication settings are specified.

## Tools and capabilities

- `search_reviews(query)` finds matching reviews by name, synonym, keyword, or category and returns URLs and conclusions.
- `list_reviews()` returns canonical topics and slugs for the full catalogue.
- `list_updates(days?)` returns recent new or revised reviews, defaulting to seven days and allowing a wider interval.
- `get_review(slug|url)` retrieves a complete review as raw Markdown.
- `get_conclusion(slug|url)` retrieves only the plain-text conclusion.
- `get_metadata(slug|url)` returns review dates, the typed subject and alternate names, and ordered citations that may include PubMed PMIDs.
- `suggest_review(intervention, goal?, references?, email?)` submits a new-review suggestion.
- `get_version()` reports package information.

## Limitations and notes

The content comes from evipedia.ai's public surfaces, so availability and freshness depend on that site. The server is mostly read-only; `suggest_review` is the stated write path. Update results default to the last seven days and are capped at 100 entries unless a broader day range is supplied.

_Full upstream README: https://allmcps.com/mcp/evipedia-mcp/readme_