Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Evipedia

by forever-healthyversion 0.1.30i★ –iRuns on your computer
Registry nameio.github.forever-healthy/evipedia-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Clinics & health

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add evipedia -- npx -y evipedia-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "evipedia": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "evipedia-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account forever-healthy, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Clinics & healthi

  • More stars than 0% of the other 1032 servers in this category
  • Published to the registry more recently than 36% of the other 1032 servers in this category
  • Basic checks equal to or better than 100% of the other 1032 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Evipedia safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.30) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Google Health MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

by thetahealthGrowing↓ 290/wk★ 1.4KUpdated yesterday

Runs on your computer✓ thetahealth.ai

FHIR MCP Server

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

by wso2Growing↓ 823/wk★ 137Updated 11 days ago

Runs on your computer

Google Health MCP

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

by davidmosiahGrowing↓ 1K/wk★ 79Updated 4 months ago

Runs on your computer

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

_2026-Forever_Healthy-573D7D.svg)

Evipedia MCP Server

A small Model Context Protocol server that lets AI agents query evipedia.ai — our continuously-updated encyclopedia of evidence reviews on health & longevity interventions — and suggest new interventions for review.

Tools

  • search_reviews(query) → matching reviews (name/synonym/keyword/category), each with its URL and conclusion
  • list_reviews() → the full catalogue as {topic, slug} pairs (canonical topic + the slug you pass to get_review/get_conclusion)
  • list_updates(days?) → the change feed, newest first: {title, slug, status, date} per recently published (new) or revised (updated) review. With no arguments it returns the last 7 days, capped at 100 entries; pass days for a wider window (e.g. days: 30)
  • get_conclusion(slug|url) → just the review's plain-text conclusion
  • get_review(slug|url) → the full review as raw Markdown
  • get_metadata(slug|url) → structured medical metadata as JSON — review dates (datePublished/dateModified/lastReviewed, a freshness signal not in the Markdown), the typed about entity with alternate names, and an ordered citation list with PubMed PMIDs

The read tools accept either a bare slug (e.g. rapamycin) or a full evipedia.ai URL (e.g. https://evipedia.ai/rapamycin) — the URL's last path segment is the slug, so a search result's URL can be passed straight through.

  • suggest_review(intervention, goal?, references?, email?) → submit a new review for an intervention to evipedia's public suggestion form (the same one at evipedia.ai/suggest)
  • get_version() → the running server's package name and version

Install (local or remote)

The server is published to npm as [`evipedia-mcp`](https://www.npmjs.com/package/evipedia-mcp) and runs over stdio via npx — no global install needed. It's also listed in the official MCP Registry as `io.github.forever-healthy/evipedia-mcp`, so MCP-aware clients can discover and install it automatically.

Client config: Local MCP (Requires Node.js ≥ 18)

{

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

For environments where a local install is not possible or desired, we also provide a hosted MCP server at https://mcp.evipedia.ai/ that can be used over HTTP.

Client config: Remote MCP via HTTP

{

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

  • Claude Code — add to your project's .mcp.json (or run claude mcp add).
  • Claude Desktop — add to claude_desktop_config.json.
  • Cursor — add to the MCP settings.

Try it

You can use the bundled `/demo` skill to smoke-test the respective connection.

It walks through the read tools (get_version, search_reviews, list_reviews, list_updates, get_review, get_conclusion, get_metadata) against live evipedia.ai data.

Architecture

The server is a thin client that only uses evipedia.ai's public endpoints. It does not depend on the evipedia content repo — the public surfaces are the API by design.

  • Fetches live from https://evipedia.ai with a small in-process cache (both JSON indexes are tiny)
  • Mostly read-only, no auth required. The one write path is suggest_review, which POSTs to evipedia's public suggestion form (Formspree)
Public API Surface

Base URL: https://evipedia.ai

EndpointDescription
GET /reviews.jsonFull catalogue: canonical_name, alternate_names[], permalink, permalink_md, permalink_meta, category, creation_date, dateModified, lastReviewed, er_conclusion
GET /search.jsonSearch index: short_topic, alternate_names, ep_keywords, ep_category, url
GET /updates.jsonChange feed, newest first: title, permalink, status (new/updated), date
GET /{permalink}.mdComplete review as raw Markdown (frontmatter + full body)
GET /{permalink}.meta.jsonFlattened medical metadata: slug, topic, url, datePublished/dateModified/lastReviewed, about (type/name/alternateName), ordered citation[] (name, url, pmid?)
GET /llms.txtAgent/human signpost — includes the stable section anchor list
GET /sitemap.xmlCanonical review URLs
GET /feed.xmlRSS feed of latest updates
Ask PopNx