Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Description from the maker (original English)
MCP Server for evipedia.ai — evidence-based reviews of health & longevity interventions
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
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-mcpPaste 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.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account forever-healthy, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (0.1.30) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Mirobody, FHIR MCP Server, Google Health MCP
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
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
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)
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.
search_reviews(query) → matching reviews (name/synonym/keyword/category), each with its URL and conclusionlist_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 conclusionget_review(slug|url) → the full review as raw Markdownget_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 PMIDsThe 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 versionThe 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" } } }
.mcp.json (or run claude mcp add).claude_desktop_config.json.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.
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.
https://evipedia.ai with a small in-process cache (both JSON indexes are tiny)suggest_review, which POSTs to evipedia's public suggestion form (Formspree)Base URL: https://evipedia.ai
| Endpoint | Description |
|---|---|
GET /reviews.json | Full catalogue: canonical_name, alternate_names[], permalink, permalink_md, permalink_meta, category, creation_date, dateModified, lastReviewed, er_conclusion |
GET /search.json | Search index: short_topic, alternate_names, ep_keywords, ep_category, url |
GET /updates.json | Change feed, newest first: title, permalink, status (new/updated), date |
GET /{permalink}.md | Complete review as raw Markdown (frontmatter + full body) |
GET /{permalink}.meta.json | Flattened medical metadata: slug, topic, url, datePublished/dateModified/lastReviewed, about (type/name/alternateName), ordered citation[] (name, url, pmid?) |
GET /llms.txt | Agent/human signpost — includes the stable section anchor list |
GET /sitemap.xml | Canonical review URLs |
GET /feed.xml | RSS feed of latest updates |