# Mitre Cwe (npm · @pipeworx/mcp-mitre-cwe)

MITRE CWE API MCP.

- Trust score: 82/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`: 85/100, [markdown](https://verifymcp.io/servers/pipeworx-io-mitre-cwe/mitre-cwe-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-mitre-cwe/mitre-cwe-mcp)
- npm · `@pipeworx/mcp-mitre-cwe`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-mitre-cwe/pipeworx-mcp-mitre-cwe.md), [page](https://verifymcp.io/servers/pipeworx-io-mitre-cwe/pipeworx-mcp-mitre-cwe)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-mitre-cwe`
- 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-mitre-cwe).
  - 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**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 725 tokens (~103/item across 7 items; 7 tools + 0 resources), lean.
  - 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**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 22% 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.

## Install

### How do I install the Mitre Cwe MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-05 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −13)

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

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

First indexed and scored.

## MCP tools (7)

### `weakness` (~160 tokens)

"What is CWE-[N]" / "look up CWE [name]" / "details on [weakness]" / "explain XSS / SQL injection / buffer overflow" / "what kind of security flaw is [X]" — fetch a single MITRE CWE (Common Weakness Enumeration) record with description, examples, mitigations, related attacks, references. Use for security analysis, vulnerability triage, threat-modeling, secure-coding training. Example IDs: 79 (XSS), 89 (SQL injection), 787 (out-of-bounds write).

Input parameters:

- `id` (string, required): CWE id (e.g. "79" or "CWE-79")
- `view` (string): Optional view id to retrieve view-specific info.

### `category` (~83 tokens)

"What CWEs fall under [category]" / "list weaknesses in the [X] family" / "memory safety weaknesses" / "input validation weaknesses" — fetch a CWE category record (a thematic grouping of related CWEs like "Memory Safety", "Input Validation", "Cryptographic Issues"). Returns the category description plus member CWE IDs.

Input parameters:

- `id` (string, required)

### `view` (~101 tokens)

"Top 25 most dangerous software weaknesses" / "OWASP Top 10 CWE mapping" / "CWE view [N]" — fetch a curated CWE view (a published, opinionated selection of weaknesses). View 1003 = simplified mapping (NVD uses this), view 1387 = Top 25, view 1344 = OWASP Top 10. Returns the view's metadata plus the included CWE IDs.

Input parameters:

- `id` (string, required)

### `children` (~92 tokens)

"CWEs derived from / under [N]" / "child weaknesses of [CWE]" / "more specific variants of [X]" — list immediate children of a CWE in the relationship tree. CWE is hierarchical; e.g. children of CWE-119 (memory bounds) include CWE-787 (out-of-bounds write) and CWE-125 (out-of-bounds read).

Input parameters:

- `id` (string, required)

### `parents` (~69 tokens)

"What's the parent CWE of [N]" / "broader weakness category for [X]" / "where does [CWE] sit in the taxonomy" — list immediate parents of a CWE in the relationship tree. Use to walk up to a more general weakness class.

Input parameters:

- `id` (string, required)

### `descendants` (~80 tokens)

"All weaknesses derived from [CWE]" / "full subtree below [N]" / "every variant of [X]" — full transitive descendants (children, grandchildren, …) of a CWE. Use for exhaustive coverage analysis — e.g. "every memory-safety weakness" via descendants of CWE-664/119.

Input parameters:

- `id` (string, required)

### `relationship` (~84 tokens)

"How is [CWE-A] related to [CWE-B]" / "relationship between two weaknesses" — fetch the directional relationship (parent/child/peer/precedes/can-precede) between two specific CWE IDs. Specialty tool; most queries are better served by children / parents / descendants.

Input parameters:

- `source_id` (string, required)
- `target_id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 66
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Mitre Cwe MCP server?

Mitre Cwe is an MCP server listed in the public MCP registry as io.github.pipeworx-io/mitre-cwe. MITRE CWE API MCP. This page covers its npm package (@pipeworx/mcp-mitre-cwe).

### Is the Mitre Cwe MCP server safe to use?

Mitre Cwe scores 82 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 Mitre Cwe MCP server expose?

Mitre Cwe exposes 7 tools: weakness, category, view, children, parents, and 2 more. Their descriptions and schemas cost roughly 669 tokens of context every time the server is loaded.

### Is the Mitre Cwe MCP server still maintained?

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

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