Evipedia MCP server

Read from the package source without running it. The installed server may list more.

• get_conclusion

  Get just the plain-text conclusion of an evidence review \u2014 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 a

• get_metadata

  Get a review's structured medical metadata as JSON: review dates (datePublished/dateModified/lastReviewed \u2014 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 dr

• get_review

  Get the full evidence review as raw Markdown \u2014 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

• get_version

  Get the running evipedia MCP server's package name and version. Useful to confirm which build is loaded.

• 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

• list_updates

  List recently published or revised evipedia.ai reviews, newest first \u2014 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. d

• 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).

• suggest_review

  Suggest a new review for evipedia.ai \u2014 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 \u2014 this sends a message to the evipedia team. Search first with search_reviews to confirm the catalogue doesn't already cover it. Only `interventio

• Code scan2 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 10 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Evipedia: common questions

Is Evipedia MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the Evipedia safety report

How do I install Evipedia?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Evipedia need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Evipedia maintained?

The last commit was 11 days ago (2026-09-09). The latest release is v0.1.30.