# Herb Tcm

> HERB 2.0 (herb.ac.cn) — Traditional Chinese Medicine herb/ingredient/target/

- name: io.github.pipeworx-io/herb-tcm
- version: 0.1.2
- connection class: R0 (autonomous)
- trust: 97/100
- quality: –/100 (not scored)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.pipeworx-io%2Fherb-tcm
- tools: https://api.protogrid.dev/v1/servers/io.github.pipeworx-io%2Fherb-tcm/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "herb-tcm": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/herb-tcm/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 99
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-97% +updated-24d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality –/100 (not scored)

Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: n/a (weight 30)

- n/a `tools.descriptions`, `tools.description_length`, `tools.schemas`, `tools.annotations`, `tools.directory_hints`, `tools.token_cost`, `tools.api_dump`: tool list unknown (behind auth, not probed, or empty)

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool list unknown

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: unknown
- tools last changed: 2026-10-10T07:30:54.896Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.pipeworx-io/herb-tcm.svg)](https://protogrid.dev/servers/io.github.pipeworx-io/herb-tcm)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-10 `forget` removed
  - Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
- 2026-10-10 `polymarket_fill_risk` removed
  - Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, and a verdict (clean|degraded|cannot_fill). BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio, profit_usd at executed size, per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L). FEES ARE NOT MODELLED HERE: vwap_fill_price/profit_usd are GROSS of Polymarket's own taker fee (rate 0.04-0.07 by category — see polymarket_edges/fees.ts), on top of which this tool prices depth-crossing cost; a thin-margin fill that looks clean here can still be net-negative after the fee.
- 2026-10-10 `herb_experiment_detail` removed
  - 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.
- 2026-10-10 `herb_experiments` removed
  - 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.
- 2026-10-10 `herb_paper_detail` removed
  - 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.
- 2026-10-10 `discover_tools` removed
  - Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).
- 2026-10-10 `remember` removed
  - Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.
- 2026-10-10 `herb_papers` removed
  - 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.
- 2026-10-10 `herb_detail` removed
  - 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`.
- 2026-10-10 `herb_browse` removed
  - 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.

Full history: https://api.protogrid.dev/v1/servers/io.github.pipeworx-io%2Fherb-tcm/changes

## Remotes

- https://gateway.pipeworx.io/herb-tcm/mcp (streamable-http, auth none, reachable true, uptime30d 0.974359)

## Packages

_none_

## Tools (0)

_none observed_