Harvest
Retrieve the complete Official MCP Registry and search GitHub repositories, code, curated catalogues, and citation chains.
A living, reproducible protocol for finding MCP servers, connectors, skills, libraries, and agents relevant to real-world evidence.
Last updated July 10, 2026 · Metadata verification snapshot completed.
Discovery pairs a technology signal with a health-workflow concept. The complete Official MCP Registry is also harvested and screened locally, so projects do not need to use our terminology to be found.
Retrieve the complete Official MCP Registry and search GitHub repositories, code, curated catalogues, and citation chains.
Run a reproducible matrix of technology signals against controlled RWE, HEOR, public-health, method, data, disease, and exposure terms.
Classify each candidate as direct RWE, enabling infrastructure, adjacent, excluded, duplicate, unavailable, or flagged.
Record the canonical source, implementation evidence, maintenance signal, provenance, limitations, and exact discovery path.
If a search wave cannot recover a known relevant project, screening stops and the discovery logic is revised.
Terms are searched as acronyms, expanded forms, plurals, and predictable variants. Broad words such as “disease,” “connector,” “FDA,” or “bias” must be paired with a stronger technology or RWE signal.
A public MCP server, connector, agent skill, library with an agent-facing interface, plugin, or orchestrated agent workflow that supports an identifiable RWE, HEOR, epidemiology, public-health, evidence-synthesis, or enabling activity.
Generic health assistants, incidental MCP mentions, nonfunctional demonstrations, duplicates, implausible bulk projects, or projects connected only by a broad disease or treatment word.
Every predefined query is run, the Official MCP Registry is fully screened, two synonym and citation-chaining rounds produce no new eligible projects, and every candidate has a recorded disposition.