SafeWeave
NPM · SAFEWEAVE-MCP · 2 COMPONENTS
Security scanner for AI-written code: SAST, secrets, dependencies, IaC, containers and DAST.
Available components
Last scanned (7 hours ago)
Scores higher than 50% of npm servers
Category Security
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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- 60% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 328 tokens (~32/item across 10 items; 8 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 21 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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/safeweave-mcp@0.7.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
get_findings ~39
Get current scan findings, optionally filtered by severity or file
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | Filter by file path |
| severity | string | – | – |
No output schema declared.
No examples provided.
get_fix_context ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | The finding ID to fix (from scan results or cloud findings) |
No output schema declared.
No examples provided.
get_security_score ~19
Get overall security posture score based on latest findings
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_dependencies ~34
Audit project dependencies for known CVEs (npm, pip, Go, Cargo)
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Project root directory |
No output schema declared.
No examples provided.
scan_file ~35
Scan a single file for security vulnerabilities (SAST + secrets)
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the file to scan |
No output schema declared.
No examples provided.
scan_project ~51
Run a full security scan on the project with all available scanners. Self-Hosted runs locally; Cloud sends to SafeWeave API.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Project root directory (defaults to current working directory) |
No output schema declared.
No examples provided.
set_profile ~23
Switch the active compliance profile
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | yes | Profile name |
No output schema declared.
No examples provided.
suggest_fix ~32
Get remediation suggestions for a specific finding
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | The finding ID to get fix suggestions for |
No output schema declared.
No examples provided.
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.
npm · safeweave-mcp
claude mcp add dev-safeweave-safeweave -- npx -y safeweave-mcp
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.