evipedia.aidev
← Back

Made for AI Integration

  

Evipedia is built for use not only by people, but by the tools people build and use — models, AI agents, research pipelines, and anything else that needs trustworthy, up-to-date evidence on health and longevity interventions.

We’ve worked to make integrating Evipedia as seamless and powerful as possible — with purpose-built tools, an AI-friendly site policy, and structured data for every review.

Agent-Friendly Content & Site Policy

Evipedia places no barriers to automated access. Our crawler policy is fully open — every agent and crawler is welcome, whether it’s an AI assistant (Grok, ChatGPT, Claude, Perplexity, and others), a search engine, or a research tool — so your integration can fetch what it needs without special arrangements.

Agents can start from /llms.txt, a machine-readable signpost to everything below, or the /openapi.yaml spec for the full API.

All content is licensed under CC BY 4.0. Use it freely, provided you credit evipedia.ai and, where practical, link back to a review’s permalink.

Structured Data on Every Review

Each review page includes schema.org MedicalWebPage structured data (JSON-LD) — the conclusion, synonyms, category, and publication date — in a machine-readable format. It also lists the review’s primary-source citations (PubMed, ClinicalTrials.gov, DOI) as structured ScholarlyArticle / MedicalStudy entries, each with its PMID / NCT / DOI identifier, so an agent can traverse straight to the underlying evidence. Agents can extract the evidence summary and its sources deterministically, without scraping prose.

Evipedia MCP Server

The Evipedia MCP server connects any Model Context Protocol client — Claude, Cursor, Grok, and others — straight to evipedia.ai. Agents can search reviews, list the full catalog, pull a review’s conclusion, full Markdown, or structured medical metadata, and suggest new interventions — no API key needed. Run it two ways:

Local (stdio) — runs on your own machine via npx (requires Node.js ≥ 18). Published to npm as evipedia-mcp and listed in the MCP Registry as io.github.forever-healthy/evipedia-mcp for automatic agent discovery:

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

Hosted (HTTP) — for environments where a local install is not possible or desired, we also provide a hosted version at https://mcp.evipedia.ai/ that can be used over HTTP:

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

Most MCP clients take the same config — e.g., Cursor’s MCP settings, or Claude Code’s .mcp.json (or run claude mcp add). For Claude Code/Desktop & Grok Build, the Evipedia plugin below sets this up for you.

Evipedia AI Plugin

The Evipedia AI plugin is the easiest way to get everything above into Claude or Grok Build (or any other environment that supports Anthropic-style marketplaces) — it wires in the MCP server plus a /demo skill in a simple install.

Published in the Forever Healthy plugin marketplace: forever-healthy/fh-plugins

Claude Desktop

forever-healthy/fh-plugins

Claude Code

/plugin marketplace add forever-healthy/fh-plugins
/plugin install evipedia@forever-healthy

Grok Build

/marketplace add forever-healthy/fh-plugins

evipedia-remote

For convenience, we have also added an evipedia-remote plugin that connects to the hosted MCP server rather than a local installation.

Evipedia Grok Bot

The Evipedia Grok Bot turns Grok into a specialized AI assistant offering an evidence-based 2nd opinion on health and longevity interventions.

More details on our Grok Bot page.

Evipedia Custom GPT

For ChatGPT users, the Evipedia Custom GPT gives the same evidence at zero setup — no install, no API key. It’s a wrapper over the public API (a ChatGPT Action pointed at our OpenAPI spec), so it can search reviews, pull a review’s conclusion or full text, and link straight back to evipedia.ai.

Use it on chatgpt.com.

Limitations

Please be aware of the “Limitations of Evipedia, AI4L & AI”