Herb Tcm
NPM · @PIPEWORX/MCP-HERB-TCM · 2 COMPONENTS
HERB 2.0 (herb.ac.cn) — Traditional Chinese Medicine herb/ingredient/target/ disease knowledge…
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-herb-tcm). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1310 tokens (~187/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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 +1
- Security disclosure: fail → unverified ▼ functional
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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-herb-tcm@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-herb-tcm |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-herb-tcm/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637390090 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:00eab7c27cf686dc00b17c0433cbe7bf23fb9103a1c761e534d80dc4e1931f3c9611d21fcf3be28237c491eeb7e759d703d57de3143ce3d60025eb141 |
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 →
herb_browse ~112
Page through HERB 2.0's full herb, ingredient, target or disease list (7,263 herbs / 49,258 ingredients / 12,933 targets / 28,212 diseases). Use herb_search instead when you already have a name to look up.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Table to browse. |
| page | number | – | 1-based page number. Defaults to 1. |
| page_size | number | – | Rows per page, max 100. Defaults to 20. |
No output schema declared.
No examples provided.
herb_detail ~445
Full record for one HERB id: herb (composition + traditional-use summary + predicted and literature target/disease links), ingredient (structure + predicted and literature target/disease links), target (curated disease associations + which herbs are statistically linked to it), or disease (which targets and herbs are statistically linked to it). Every relationship row carries an evidence_tier. computational_prediction means a statistical or database-mined association with NO clinical or experimental confirmation — it is a hypothesis, not proof the herb/ingredient treats the condition. traditional_use reflects historical TCM practice, not a trial. Only human_clinical rows come from a paper that studied humans. A predicted herb-disease or herb-target edge (evidence_tier computational_prediction) is a screening hit from expression-overlap statistics, not proof of efficacy — never present it as "HERB shows herb X treats disease Y" without saying it is a prediction. Relationship tables are paged: each comes back as {total, offset, limit, returned, truncated, rows} with the TRUE upstream row count in `total` (a well-studied herb can have thousands of predicted disease rows — 25 are returned by default). truncated:true means more rows exist; page with offset, or narrow with `sections`.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Must match the id's prefix. |
| id | string | yes | HERB id, e.g. HERB004520 (herb), HBIN016960 (ingredient), HBTAR000001 (target), HBDIS000001 (disease). |
| limit | number | – | Max rows returned per relationship table (herb_ingredient, herb_target, herb_disease, ingredient_target, ingredient_disease, target_disease, drug_paper_target, drug_paper_disease). Default 25, max 20… |
| offset | number | – | 0-based row offset applied to each relationship table. Default 0. |
| sections | array | – | Return only these sections — e.g. ["summary","herb_ingredient"] for composition without pulling hundreds of predicted disease rows. Omit for all sections. |
No output schema declared.
No examples provided.
herb_experiment_detail ~104
Differential-expression results for one HERB transcriptomic experiment: top up/down-regulated genes and enriched GO terms / KEGG pathways, plus connectivity-map hit counts (compounds/knockdowns/overexpression signatures matching the expression pattern). Every row is evidence_tier computational_prediction — this is a statistical enrichment over one dataset, not a validated mechanism or a clinical finding.
| Name | Type | Req | Description |
|---|---|---|---|
| experiment_id | string | yes | HERB experiment id, e.g. HBEXP000001. |
No output schema declared.
No examples provided.
herb_experiments ~118
List HERB's transcriptomic experiments (herb/ingredient treatment vs. control, GEO-deposited) — the raw evidence behind the differential-expression predictions in herb_experiment_detail. Filter by drug type, species or platform.
| Name | Type | Req | Description |
|---|---|---|---|
| drug_type | string | – | – |
| experiment_type | string | – | – |
| limit | number | – | Max rows to return, default 25, max 100. |
| offset | number | – | 0-based offset for paging past the first `limit` rows. |
| species | string | – | – |
No output schema declared.
No examples provided.
herb_paper_detail ~105
One reference's bibliographic record (journal, PubMed id, experiment type, phenotype) plus the specific targets/diseases that paper reports, tagged evidence_tier human_clinical or laboratory from the paper's own experiment type. Use the Paper id from a drug_paper_target/drug_paper_disease row (herb_detail) or from herb_papers.
| Name | Type | Req | Description |
|---|---|---|---|
| paper_id | string | yes | HERB reference id, e.g. HBREF000003. |
No output schema declared.
No examples provided.
herb_papers ~205
List PubMed-cited papers in HERB's reference index — the literature backing herb/ingredient-target and -disease associations. Each row is tagged evidence_tier human_clinical (its "Experiment type" includes "Clinical Experiment") or laboratory (cell/animal studies only). Filter by drug type or experiment type, or leave both blank to page through all ~2,000 references.
| Name | Type | Req | Description |
|---|---|---|---|
| drug_type | string | – | Restrict to papers about herbs or about single ingredients. |
| experiment_type | string | – | Upstream free-text filter, e.g. "Clinical Experiment", "Animal Experiment", "Cell Experiment". |
| limit | number | – | Max rows to return, default 25, max 100 (the full index is fetched upstream and sliced here). |
| offset | number | – | 0-based offset for paging past the first `limit` rows. |
| sort_by | string | – | Upstream sort field (optional; upstream default order is used if omitted). |
No output schema declared.
No examples provided.
herb_search ~166
Search HERB 2.0 for a herb, ingredient, gene target or disease by Chinese name, pinyin, English name, Latin name, gene alias or HERB id — e.g. "板蓝根", "banlangen", "Dyers Woad" and "BAN LAN GEN" all resolve the same herb record. Returns matching ids to pass to herb_detail. Does not itself carry evidence tiers (it is a name lookup, not a relationship).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Which table to search. Defaults to "herb". |
| keyword | string | yes | Search term: Chinese characters, pinyin, English/Latin name, gene name/alias, disease name, or a HERB id (e.g. HERB004520, HBIN016960). |
No output schema declared.
No examples provided.
How do I install the Herb Tcm MCP server?
Herb Tcm runs locally as an npm package, launched with npx -y @pipeworx/mcp-herb-tcm. 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-herb-tcm
claude mcp add pipeworx-io-herb-tcm -- npx -y @pipeworx/mcp-herb-tcm
What is the Herb Tcm MCP server?
Herb Tcm is an MCP server listed in the public MCP registry as io.github.pipeworx-io/herb-tcm. HERB 2.0 (herb.ac.cn), Traditional Chinese Medicine herb/ingredient/target/ disease knowledge… This page covers its npm package (@pipeworx/mcp-herb-tcm).
Is the Herb Tcm MCP server safe to use?
Herb Tcm 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 Herb Tcm MCP server expose?
Herb Tcm exposes 7 tools: herb_search, herb_browse, herb_detail, herb_papers, herb_paper_detail, and 2 more. Their descriptions and schemas cost roughly 1,255 tokens of context every time the server is loaded.
Is the Herb Tcm MCP server still maintained?
Herb Tcm 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 Herb Tcm MCP server under?
Herb Tcm declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.