# SafeWeave (npm · safeweave-mcp)

Security scanner for AI-written code: SAST, secrets, dependencies, IaC, containers and DAST.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.safeweave.dev`: 38/100, [markdown](https://verifymcp.io/servers/dev-safeweave-safeweave/mcp.md), [page](https://verifymcp.io/servers/dev-safeweave-safeweave/mcp)
- npm · `safeweave-mcp`: 75/100 (this document), [markdown](https://verifymcp.io/servers/dev-safeweave-safeweave/safeweave-mcp.md), [page](https://verifymcp.io/servers/dev-safeweave-safeweave/safeweave-mcp)

## Channel facts

- Registry: `npm`
- Package: `safeweave-mcp`
- Version: `0.7.5`
- 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**: 98/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.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - 60% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 328 tokens (~32/item across 10 items; 8 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 SafeWeave MCP server?

SafeWeave runs locally as an npm package, launched with npx -y safeweave-mcp. 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 dev-safeweave-safeweave -- npx -y safeweave-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-safeweave-safeweave": {
      "command": "npx",
      "args": [
        "-y",
        "safeweave-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-safeweave-safeweave": {
      "command": "npx",
      "args": [
        "-y",
        "safeweave-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-safeweave-safeweave -- npx -y safeweave-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-safeweave-safeweave --command npx --arg -y --arg safeweave-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-safeweave-safeweave:
    command: "npx"
    args: ["-y", "safeweave-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-safeweave-safeweave": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "safeweave-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-safeweave-safeweave -t stdio -c npx -a -y safeweave-mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-safeweave-safeweave": {
      "command": "npx",
      "args": [
        "-y",
        "safeweave-mcp"
      ]
    }
  }
}
```

## 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 75, +1)

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

### 2026-11-02 (score 74, +1)

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

### 2026-10-30 (score 73, +1)

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

### 2026-10-28 (score 72, +1)

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

### 2026-10-26 (score 71, +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-10-24 (score 70, +1)

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

### 2026-10-22 (score 69, +1)

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

### 2026-10-21 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (8)

### `scan_file` (~35 tokens)

Scan a single file for security vulnerabilities (SAST + secrets)

Input parameters:

- `file_path` (string, required): Path to the file to scan

### `scan_project` (~51 tokens)

Run a full security scan on the project with all available scanners. Self-Hosted runs locally; Cloud sends to SafeWeave API.

Input parameters:

- `directory` (string): Project root directory (defaults to current working directory)

### `scan_dependencies` (~34 tokens)

Audit project dependencies for known CVEs (npm, pip, Go, Cargo)

Input parameters:

- `directory` (string): Project root directory

### `get_findings` (~39 tokens)

Get current scan findings, optionally filtered by severity or file

Input parameters:

- `file` (string): Filter by file path
- `severity` (string)

### `set_profile` (~23 tokens)

Switch the active compliance profile

Input parameters:

- `profile` (string, required): Profile name

### `get_security_score` (~19 tokens)

Get overall security posture score based on latest findings

### `suggest_fix` (~32 tokens)

Get remediation suggestions for a specific finding

Input parameters:

- `finding_id` (string, required): The finding ID to get fix suggestions for

### `get_fix_context` (~85 tokens)

Read the vulnerable file, extract the code around the finding, and return a structured fix request that you (the AI) should use to generate and apply a code fix. This is the primary way to fix security issues — call this, then edit the file based on the response.

Input parameters:

- `finding_id` (string, required): The finding ID to fix (from scan results or cloud findings)

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 70
- 2026-10-24: 70
- 2026-10-23: 69
- 2026-10-22: 69
- 2026-10-21: 68
- 2026-10-20: 53
- 2026-10-19: 52

## Common questions

### What is the SafeWeave MCP server?

SafeWeave is an MCP server listed in the public MCP registry as dev.safeweave/safeweave. Security scanner for AI-written code: SAST, secrets, dependencies, IaC, containers and DAST. This page covers its npm package (safeweave-mcp).

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

SafeWeave scores 75 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. 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 SafeWeave MCP server expose?

SafeWeave exposes 8 tools: scan_file, scan_project, scan_dependencies, get_findings, set_profile, and 3 more. Their descriptions and schemas cost roughly 318 tokens of context every time the server is loaded.

### Is the SafeWeave MCP server still maintained?

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

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