Ext Ops Panel
Open dashboard
Comparison

phenoworks-mcp vs Forever Healthy Evidence MCP

phenoworks-mcp is an MCP server published by OpenSciML. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Forever Healthy Evidence MCP is an MCP server published by forever-healthy. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacephenoworks-mcpForever Healthy Evidence MCP
PyPI (MCP servers) Listed
Version: 0.5.1
Downloads/month (PyPI): 547
Downloads/week (PyPI): 116
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.43
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

phenoworks-mcp vs Forever Healthy Evidence MCP
Factphenoworks-mcpForever Healthy Evidence MCP
Marketplaces that list it11
Last release (differs)2026-10-27 (worse)2026-11-12 (better)
Where it runs (differs)On your machine (phenoworks-mcp)On your machine (evidence-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/opensciml/phenoworksgithub.com/forever-healthy/evidence-mcp
Changes in the last 7 days (differs)014
First seen (differs)2026-10-132026-11-09

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

phenoworks-mcp

In its own words, on PyPI (MCP servers):

Connect AI assistants to PhenoWorks projects, datasets, and analysis pipelines through MCP.

Forever Healthy Evidence MCP

In its own words, on Official MCP Registry:

Medical literature research for agents: source library, claim verification, PubMed, trials, fetch

How to run each

phenoworks-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Forever Healthy Evidence MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio evidence-mcp -- npx -y evidence-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: phenoworks-mcp · What it can do: Forever Healthy Evidence MCP · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built