Symmap
NPM · @PIPEWORX/MCP-SYMMAP · 2 COMPONENTS
SymMap v2 — Traditional Chinese Medicine association graph from symmap.org (Beijing University of…
Available components
Last scanned (8 hours ago)
Scores higher than 65% 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-symmap). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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
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.
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.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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-symmap@0.2.0
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-symmap |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-symmap/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560357774 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4105df676bcb44e2fb4ca8008ce29d8d701b70364956973efeba01c8fc3730905dce608a29d435acc453d00f6f324055a823c6a92f1d6870ba834c3f9 |
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 →
symmap_herb ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| herb | string | yes | Herb name in any script (人参 / Renshen / Ginseng / Ginseng Radix Et Rhizoma) or SMHB id (SMHB00336) |
No output schema declared.
No examples provided.
symmap_herb_ingredients ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| herb | string | yes | Herb name in any script or SMHB id |
| limit | number | – | Max ingredients returned, 1-200 (default 50) |
No output schema declared.
No examples provided.
symmap_herb_symptoms ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| herb | string | yes | Herb name in any script or SMHB id |
| limit | number | – | Max symptoms and syndromes returned each, 1-200 (default 50) |
No output schema declared.
No examples provided.
symmap_ingredient ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| herbs_limit | number | – | Max source herbs returned, 1-200 (default 25) |
| ingredient | string | yes | Ingredient name (e.g. "quercetin") or SMIT id (SMIT00013) |
| targets_limit | number | – | Max protein targets returned, 1-200 (default 50) |
No output schema declared.
No examples provided.
symmap_search ~230
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | 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 | yes | Name to look up — e.g. "ginseng", "人参", "Renshen", "quercetin", "IL6", "malaria", "insomnia" |
No output schema declared.
No examples provided.
symmap_symptom_herbs ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max herbs returned per symptom, 1-100 (default 25) |
| symptom | string | yes | Symptom name — TCM (e.g. 痹痛 / "Bi Tong") for system:"tcm", modern medical (e.g. "insomnia", "Arthritic Pains") for system:"modern" |
| system | string | yes | Which symptom vocabulary the name belongs to. They are distinct in SymMap; this tool never merges them. |
No output schema declared.
No examples provided.
symmap_target_diseases ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max diseases returned, 1-200 (default 50) |
| target | string | yes | Gene symbol (e.g. "IL6", "A2M") or SMTT id (SMTT00001) |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-symmap
claude mcp add pipeworx-io-symmap -- npx -y @pipeworx/mcp-symmap
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.