
Herb Tcm MCP server
online · 100% uptimeHERB 2.0 (herb.ac.cn) — Traditional Chinese Medicine herb/ingredient/target/ disease knowledge…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Herb Tcm yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Herb Tcm tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Herb Tcm compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 39 ms
- faster than 94% of 30,031 servers
Release history: 6 versions in the registry since 2026-09-16, latest 2026-11-02, typically one every 4 days.
Install Herb Tcm in Claude Code, Cursor or VS Code
claude mcp add --transport http herb-tcm https://gateway.pipeworx.io/herb-tcm/mcp
What the publisher says
From the Herb Tcm repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/herb-tcm
HERB 2.0's Traditional Chinese Medicine knowledge base — herbs, ingredients, gene targets, diseases, PubMed-cited papers and GEO transcriptomic experiments — proxied live from herb.ac.cn, with every relationship row tagged an evidence_tier so a statistical prediction is never mistaken for proof of efficacy.
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
Tools
Chinese characters, pinyin, English/Latin names, gene names/aliases, disease names, or a HERB id itself. category is one of herb / ingredient / target / disease (default herb).
- herb_search(keyword, category?) — resolve a name to an id. Accepts
herb/ingredient/target/disease list (7,263 / 49,258 / 12,933 / 28,212 rows respectively).
- herbbrowse(category, page?, pagesize?) — page through the full
for one id: composition, traditional-use summary, and every predicted or literature-backed target/disease relationship, each carrying its evidencetier. Relationship tables are paged (fleet #1399 — an unpaged well-studied herb ran to 806 KB): each comes back as {total, offset, limit, returned, truncated, rows} where total is the TRUE upstream row count and truncated: true says more rows exist — so a 25-row slice can never be mistaken for 25 rows existing. limit defaults to 25 (the pack's precedent, set by herbpapers), max 200; offset pages; sections (e.g. ["summary","herbingredient"]) fetches composition without pulling thousands of predicted disease rows, and an unknown section name errors loudly rather than silently returning nothing. We chose client-side slicing over a sections-only design because detailapi has no server-side paging (one upstream call returns everything regardless), so the slice costs nothing extra and the envelope keeps the caller honest. ingredient_alias (a small synonym list) is never paged.
- herb_detail(id, category, limit?, offset?, sections?) — the full record
list PubMed-cited references, each tagged human_clinical or laboratory.
- herbpapers(drugtype?, experimenttype?, sortby?, limit?, offset?) —
the specific targets/diseases it reports.
- herbpaperdetail(paper_id) — one reference's bibliographic record plus
— list GEO-deposited herb/ingredient-vs-control transcriptomic experiments.
- herbexperiments(drugtype?, species?, experiment_type?, limit?, offset?)
for one experiment: top up/down genes, enriched GO/KEGG terms, connectivity-map hit counts. Always evidencetier: computationalprediction.
- herbexperimentdetail(experiment_id) — differential-expression results
Evidence tiers
Every relationship row carries one of:
herbtarget / herbdisease (statistical enrichment, p-value + FDRBH columns), ingredienttarget / ingredientdisease / targetdisease (curated cross-references with no clinical backing) and every herbexperimentdetail row are computationalprediction. drugpapertarget / drugpaperdisease (PubMed-cited) are split into humanclinical or laboratory by resolving each cited paper's own "Experiment type" — see Data sources below for how.
Auth
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Herb Tcm: common questions
- Is Herb Tcm MCP server safe?
- Mostly: it is graded B (77/100). Read the Herb Tcm safety report
- How do I install Herb Tcm?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Herb Tcm need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Herb Tcm maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v0.2.1.
- Is Herb Tcm up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Herb Tcm compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 39 ms (faster than 94% of 30,031 servers). Full comparison.