Openremedies
NPM · @PIPEWORX/MCP-OPENREMEDIES · 2 COMPONENTS
OpenRemedies is a lookup of sourced treatment records for a condition: approved medicines by…
Available components
Last scanned (4 hours ago)
Scores higher than 72% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-openremedies). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 883 tokens (~110/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 4 Nov 26 −26
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-openremedies@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-openremedies |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-openremedies/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685135036 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cfe8007ebea541aa5c76452210020a7854cb7977ffb9f28f2005825290090e4ae0681318c647ce8b39a41b75c8148d96f1c8e75dcb533d7e6b96a9337 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_trials ~130
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 eligibility. Sourced from OpenRemedies (ClinicalTrials.gov registry records).
| Name | Type | Req | Description |
|---|---|---|---|
| condition_id | number | – | Condition id from resolve_condition |
| country | string | – | – |
| limit | number | – | – |
| offset | number | – | – |
| phase | string | – | – |
| status | string | – | e.g. recruiting, not_yet_recruiting |
| substance_id | number | – | Substance id from resolve_substance |
No output schema declared.
No examples provided.
get_condition_options ~159
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 development, and recruiting clinical trials. Every row carries a citation and source locator. This is a lookup of sourced records, never a recommendation. Sourced from OpenRemedies, which draws on national medicines registers and the ClinicalTrials.gov registry plus herbal and supplement monographs; call get_coverage for the current list of registers and jurisdictions.
| Name | Type | Req | Description |
|---|---|---|---|
| condition_id | number | yes | Condition id from resolve_condition |
| jurisdiction | string | – | Jurisdiction filter, e.g. US or EU |
| limit | number | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
get_coverage ~56
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 counts. The source of truth for coverage figures.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_evidence ~76
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 NCCIH herb fact sheets).
| Name | Type | Req | Description |
|---|---|---|---|
| assertion_id | number | yes | Assertion id from get_condition_options or get_substance_uses |
No output schema declared.
No examples provided.
get_related_concepts ~77
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 of clinical relatedness. Sourced from OpenRemedies (MONDO disease hierarchy).
| Name | Type | Req | Description |
|---|---|---|---|
| condition_id | number | yes | Condition id from resolve_condition |
No output schema declared.
No examples provided.
get_substance_uses ~113
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 national and regional medicines registers; call get_coverage for the current list of registers and jurisdictions.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | Jurisdiction filter, e.g. US or EU |
| limit | number | – | – |
| offset | number | – | – |
| substance_id | number | yes | Substance id from resolve_substance |
No output schema declared.
No examples provided.
resolve_condition ~109
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 trials for <condition>" question: returns the condition_id the other tools take. Sourced from OpenRemedies (MONDO-mapped condition concepts).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max candidates to return |
| q | string | yes | Condition name, abbreviation, lay term, or misspelling |
No output schema declared.
No examples provided.
resolve_substance ~109
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> used for or approved for" question: returns the substance_id the other tools take. Sourced from OpenRemedies (RxNorm-mapped substances).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max candidates to return |
| q | string | yes | Generic, brand, or botanical name |
No output schema declared.
No examples provided.
How do I install the Openremedies MCP server?
Openremedies runs locally as an npm package, launched with npx -y @pipeworx/mcp-openremedies. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-openremedies
claude mcp add pipeworx-io-openremedies -- npx -y @pipeworx/mcp-openremedies
What is the Openremedies MCP server?
Openremedies is an MCP server listed in the public MCP registry as io.github.pipeworx-io/openremedies. OpenRemedies is a lookup of sourced treatment records for a condition: approved medicines by… This page covers its npm package (@pipeworx/mcp-openremedies).
Is the Openremedies MCP server safe to use?
Openremedies scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Openremedies MCP server expose?
Openremedies exposes 8 tools: resolve_condition, resolve_substance, get_condition_options, get_substance_uses, find_trials, and 3 more. Their descriptions and schemas cost roughly 829 tokens of context every time the server is loaded.
Is the Openremedies MCP server still maintained?
Openremedies is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Openremedies MCP server under?
Openremedies declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.