@pipeworx/openremedies

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/openremedies’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 8

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.

(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 flip still pending (fleet #3443)

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. The origin in src/index.ts still points at staging.openremedies.com because the apex is not cut over; flipping ORIGIN to https://openremedies.com/mcp and adding a registry-api /uptime row stay launch items 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.

Tools

• resolve_condition — Resolve a condition name/abbreviation/lay term/misspelling to condition concepts. Ambiguity is exposed as multiple candidates, never merged. First step for any “medications, treatments or clinical tri
• resolve_substance — Resolve a drug/herb/supplement name (generic, brand, botanical) to substance records; salt/form family pointers included, labeled, never merged. First step for any “what is <drug / herb / supplement>
• get_condition_options — All medications and treatments on record for a condition, in five fixed sections: approved medicines (regulatory records only, by country or region), documented off-label use, herbs/supplements, in de
• get_substance_uses — Approvals by jurisdiction (verbatim + normalized status), verbatim indications, and evidence assertions for a substance and its labeled salt/form family. Sourced from OpenRemedies, which draws on nati
• find_trials — Registry trials filtered by condition/substance/status/phase/country. Recruiting and not-yet-recruiting are separate; unknown local recruitment stays unknown; eligibility text never declares eligibili
• get_related_concepts — Broader, subtype, and sibling condition concepts for a condition, each labeled by its structural relationship (type of / subtype / related type). Derived from the disease hierarchy — not an assertion
• get_evidence — One full evidence assertion with verbatim finding, direction, certainty basis, license, and complete provenance. Sourced from OpenRemedies (herbal monographs, Europe PMC, NIH dietary-supplement and NC
• get_coverage — What is and is NOT covered by OpenRemedies: the current list of source registers and how many jurisdictions they span, per-source freshness, jurisdiction matrix (explicit not-covered rows), evidence c