# Symmap (npm · @pipeworx/mcp-symmap)

SymMap v2 — Traditional Chinese Medicine association graph from symmap.org (Beijing University of…

- Trust score: 80/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-symmap/symmap-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-symmap/symmap-mcp)
- npm · `@pipeworx/mcp-symmap`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-symmap/pipeworx-mcp-symmap.md), [page](https://verifymcp.io/servers/pipeworx-io-symmap/pipeworx-mcp-symmap)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-symmap`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-symmap).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1207 tokens (~172/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Symmap MCP server?

Symmap runs locally as an npm package, launched with npx -y @pipeworx/mcp-symmap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-symmap -- npx -y @pipeworx/mcp-symmap
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-symmap": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-symmap"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-symmap": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-symmap"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-symmap -- npx -y @pipeworx/mcp-symmap
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-symmap": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-symmap"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-symmap --command npx --arg -y --arg @pipeworx/mcp-symmap
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-symmap:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-symmap"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-symmap": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-symmap"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-symmap -t stdio -c npx -a -y @pipeworx/mcp-symmap
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-symmap": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-symmap"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-30 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (7)

### `symmap_search` (~230 tokens)

Resolve a name to SymMap v2 (symmap.org, Beijing University of Chinese Medicine) entity records and ids across the Traditional Chinese Medicine association graph: herbs, ingredients (molecules), protein targets (genes), TCM symptoms, modern medical symptoms, TCM syndromes, diseases. Accepts Chinese characters, pinyin, Latin or English names, gene symbols, disease names. Returns the SMHB/SMIT/SMTT/SMTS/SMMS/SMSY/SMDE ids the relationship tools take. SymMap records associations, not efficacy.

Input parameters:

- `entity` (string, required): Which entity class to search. tcm_symptom is the traditional vocabulary (SMTS), mm_symptom the modern medical one (SMMS) — they are distinct in SymMap and here.
- `limit` (number): Max matches returned, 1-50 (default 10)
- `query` (string, required): Name to look up — e.g. "ginseng", "人参", "Renshen", "quercetin", "IL6", "malaria", "insomnia"

### `symmap_herb` (~137 tokens)

Full record for one of the 698 herbs in SymMap v2 (symmap.org): Chinese/pinyin/Latin/English names, TCM properties (nature/flavour), meridians, drug class, used part — bilingual, answered from the SymMap v2.0 published herb table. Accepts any name form or a SMHB id. Traditional TCM attributes describe traditional use, not clinically demonstrated effect.

Input parameters:

- `herb` (string, required): Herb name in any script (人参 / Renshen / Ginseng / Ginseng Radix Et Rhizoma) or SMHB id (SMHB00336)

### `symmap_herb_ingredients` (~119 tokens)

Chemical ingredients (molecules) identified in a Traditional Chinese Medicine herb, from SymMap v2 (symmap.org) — with PubChem CID, CAS number and oral-bioavailability score per molecule. Every edge carries evidence_tier and evidence_basis. Constituent presence is a laboratory identification; it is NOT evidence the herb or the molecule treats anything.

Input parameters:

- `herb` (string, required): Herb name in any script or SMHB id
- `limit` (number): Max ingredients returned, 1-200 (default 50)

### `symmap_herb_symptoms` (~160 tokens)

Traditional indications of a Traditional Chinese Medicine herb from SymMap v2 (symmap.org): the TCM symptoms (SMTS) and TCM syndromes (SMSY) it is traditionally used for, per the Chinese Pharmacopoeia as curated by SymMap. These are TRADITIONAL-USE records (evidence_tier on every edge), not clinical evidence, and TCM symptoms are kept separate from modern medical symptoms — use symmap_symptom_herbs with system:"modern" to enter from the modern vocabulary.

Input parameters:

- `herb` (string, required): Herb name in any script or SMHB id
- `limit` (number): Max symptoms and syndromes returned each, 1-200 (default 50)

### `symmap_symptom_herbs` (~213 tokens)

Herbs traditionally associated with a symptom in SymMap v2 (symmap.org). system:"tcm" looks up a Traditional Chinese Medicine symptom (SMTS) directly; system:"modern" starts from a modern medical symptom (SMMS), returns its curated TCM-symptom crosswalk, then the herbs per mapped TCM symptom — the two vocabularies and the mapping hop stay explicit, never merged. Every hop carries evidence_tier; a traditional-use association is not evidence of effectiveness.

Input parameters:

- `limit` (number): Max herbs returned per symptom, 1-100 (default 25)
- `symptom` (string, required): Symptom name — TCM (e.g. 痹痛 / "Bi Tong") for system:"tcm", modern medical (e.g. "insomnia", "Arthritic Pains") for system:"modern"
- `system` (string, required): Which symptom vocabulary the name belongs to. They are distinct in SymMap; this tool never merges them.

### `symmap_ingredient` (~152 tokens)

One Traditional Chinese Medicine ingredient (molecule) from SymMap v2 (symmap.org): its protein targets with literature evidence (PubMed-cited edges are tier "laboratory", uncited ones "computational_prediction") and the herbs it has been identified in. A target association is a molecular finding or a prediction — NOT evidence the ingredient treats any condition.

Input parameters:

- `herbs_limit` (number): Max source herbs returned, 1-200 (default 25)
- `ingredient` (string, required): Ingredient name (e.g. "quercetin") or SMIT id (SMIT00013)
- `targets_limit` (number): Max protein targets returned, 1-200 (default 50)

### `symmap_target_diseases` (~143 tokens)

Diseases associated with a protein target (gene) in SymMap v2 (symmap.org), with OMIM/Orphanet identifiers where the association comes from human genetics. Every edge carries evidence_tier: human_clinical for OMIM/Orphanet-backed gene–disease links, computational_prediction otherwise. A gene–disease link says NOTHING about any herb or ingredient treating the disease.

Input parameters:

- `limit` (number): Max diseases returned, 1-200 (default 50)
- `target` (string, required): Gene symbol (e.g. "IL6", "A2M") or SMTT id (SMTT00001)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-symmap/pipeworx-mcp-symmap#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Symmap MCP server?

Symmap is an MCP server listed in the public MCP registry as io.github.pipeworx-io/symmap. SymMap v2, Traditional Chinese Medicine association graph from symmap.org (Beijing University of… This page covers its npm package (@pipeworx/mcp-symmap).

### Is the Symmap MCP server safe to use?

Symmap scores 80 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 Symmap MCP server expose?

Symmap exposes 7 tools: symmap_search, symmap_herb, symmap_herb_ingredients, symmap_herb_symptoms, symmap_symptom_herbs, and 2 more. Their descriptions and schemas cost roughly 1,154 tokens of context every time the server is loaded.

### Is the Symmap MCP server still maintained?

Symmap 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 Symmap MCP server under?

Symmap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-symmap
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-symmap
- Repository: https://github.com/pipeworx-io/mcp-symmap
- Website: https://pipeworx.io/packs/symmap
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-symmap/pipeworx-mcp-symmap.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-symmap/pipeworx-mcp-symmap.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-symmap/pipeworx-mcp-symmap