# Mesh (npm · @pipeworx/mcp-mesh)

NLM MeSH (Medical Subject Headings) MCP.

- Trust score: 84/100 (high trust)
- Change this week: +3
- 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-mesh/mesh-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-mesh/mesh-mcp)
- npm · `@pipeworx/mcp-mesh`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-mesh/pipeworx-mcp-mesh.md), [page](https://verifymcp.io/servers/pipeworx-io-mesh/pipeworx-mcp-mesh)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-mesh`
- Version: `0.2.1`
- 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-mesh).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 427 tokens (~142/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

## Install

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

Mesh runs locally as an npm package, launched with npx -y @pipeworx/mcp-mesh. 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-mesh -- npx -y @pipeworx/mcp-mesh
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-11-04 (score 84, +15)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: unverified → fail

### 2026-11-03 (score 69, −12)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

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

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `search_descriptors` (~155 tokens)

Search NLM MeSH descriptors by a disease/drug/concept term (e.g. "diabetes", "aspirin", "myocardial infarction"). Returns the matching MeSH descriptor IDs (Dxxxxxxx) — the controlled-vocabulary headings used to index PubMed. The core free-text-to-MeSH lookup. Keyless.

Input parameters:

- `limit` (number): Max results (default 10, max 25).
- `match` (string): Match mode against descriptor labels: "exact", "contains", or "startswith". Default "contains".
- `text` (string, required): A disease, drug, or biomedical concept term, e.g. "diabetes", "aspirin", "myocardial infarction".

### `get_descriptor` (~113 tokens)

Get full detail for a MeSH descriptor by its ID (e.g. "D003920" = Diabetes Mellitus): its preferred label, entry terms (synonyms MeSH indexes under it), allowable qualifiers (subheadings like "drug therapy", "epidemiology"), and related see-also headings. Keyless.

Input parameters:

- `mesh_id` (string, required): A MeSH descriptor ID, e.g. "D003920" (Diabetes Mellitus) or "D001241" (Aspirin).

### `resolve_term` (~108 tokens)

Map a free-text term or everyday synonym to its canonical MeSH descriptor(s) — the preferred heading to use when searching PubMed. Tries an exact descriptor match first; if none, falls back to a fuzzy contains match (flagged fuzzy). Keyless.

Input parameters:

- `limit` (number): Max matches (default 10, max 25).
- `text` (string, required): A term or synonym to canonicalize, e.g. "aspirin", "high blood pressure", "diabetes".

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 69
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### What is the Mesh MCP server?

Mesh is an MCP server listed in the public MCP registry as io.github.pipeworx-io/mesh. NLM MeSH (Medical Subject Headings) MCP. This page covers its npm package (@pipeworx/mcp-mesh).

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

Mesh scores 84 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 Mesh MCP server expose?

Mesh exposes 3 tools: search_descriptors, get_descriptor, resolve_term. Their descriptions and schemas cost roughly 376 tokens of context every time the server is loaded.

### Is the Mesh MCP server still maintained?

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

Mesh 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-mesh
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-mesh
- Repository: https://github.com/pipeworx-io/mcp-mesh
- Website: https://pipeworx.io/packs/mesh
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-mesh/pipeworx-mcp-mesh.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-mesh/pipeworx-mcp-mesh.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-mesh/pipeworx-mcp-mesh