OpenRemedies

OpenRemedies is a lookup of sourced treatment records (approved, off-label, supplements, in development, recruiting). It never recommends treatment, diagnoses, doses, or declares trial eligibility. Every record carries a citation; empty results mean no records in covered sources, not that no treatments exist. Built on pipeworx.

Part of Pipeworx — an MCP gateway connecting AI agents to 1867+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

(That paragraph is the medical-content posture from the OpenRemedies MCP endpoint's initialize.instructions, preserved verbatim per fleet #1392. Keep it word-for-word in any public catalog entry for this pack.)

This pack proxies to the OpenRemedies MCP endpoint (Bruce's free treatment-lookup product, repo b-gutman/openremedies). It is keyless, read-only public data; OpenRemedies applies its own rate limiting at its Worker. Every response carries meta with source citations, per-source freshness, data_version, and coverage notes.

Tools

Typical flow: resolve_condition("migraine") → condition_id → get_condition_options(condition_id); or resolve_substance("sumatriptan") → substance_id → get_substance_uses(substance_id).

get_related_concepts takes the same condition_id and answers "what else should I look at" — it returns an empty list for concepts with no hierarchy neighbours carrying records (e.g. psoriasis, atopic eczema), which means no neighbours in the covered hierarchy, not that none exist.

Listed; origin flipped to the apex (fleet #3511)

Bruce lifted the unlisted hold for search and routing on 2026-10-21. The pack is in the catalog, in search_packs and on routing menus. On 2026-10-26 the OpenRemedies apex began answering (it had returned 522 that morning), and ORIGIN in src/index.ts now points at it. On the same calls the apex and the former staging host returned identical tools/list and get_coverage bodies, so the apex is currently the same deployment. It still reports a staging version, so every response keeps its deployment notice until the upstream reports a production version. Adding a registry-api /uptime row remains a launch item for the OpenRemedies PM.

The tool definitions in src/index.ts are copied from the endpoint's tools/list. If OpenRemedies changes its tool surface, update them to match; nothing syncs them automatically. Coverage figures (sources, jurisdictions) come from get_coverage; never hard-code them in a description.

Environment disclosure (fleet #3660)

Every response carries a top-level deployment object (environment, upstream_version, upstream_host, notice). It is derived, not written by hand: the pack reads the upstream's own reported version and the host it called. A staging version or host yields non-production with a notice that promises no uptime or freshness;

... View full README on GitHub