Openremedies MCP server

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 1875+ 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: resolvecondition("migraine") → conditionid → getconditionoptions(conditionid); or resolvesubstance("sumatriptan") → substanceid → getsubstanceuses(substanceid).

getrelatedconcepts 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.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "openremedies": {
      "url": "https://gateway.pipeworx.io/openremedies/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.