Sunstone Weave: Local Semantic Code Search
NPM · BLACKWINDOW-WEAVE-MCP
Semantic search over local folders of code and docs, with a code-search encoder running on your CPU.
Available components
Last scanned (17 hours ago)
Scores higher than 52% of npm servers
Category Code Search and Documentation
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 43 of 159 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 275 tokens (~68/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 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.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 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.
- 14 Oct 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.
- 13 Oct 26 +6
- Stability: unverified → 0.43 ▲ functional
- 1 Oct 26 +25
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.88 ▲ functional
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 24 Oct 2026 · Analysed npm/blackwindow-weave-mcp@0.1.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 159 packages
| Packages resolved | 159 |
|---|---|
| Stale | 43 |
| 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 →
weave_folder Weave a folder ~114
Index a folder on this machine (source code and docs) for semantic search, or bring its index up to date: only files that changed since the last run are read again. Call it once per project. The first run downloads the 33M-parameter encoder (133 MB) and embeds every passage on the CPU; a run longer than 25 s continues in the background and weave_list reports its progress.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path of the folder, or a path relative to the server's working directory |
No output schema declared.
No examples provided.
weave_forget Forget a woven folder ~37
Delete a folder's index from this machine. The folder's own files are not touched.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The woven folder |
No output schema declared.
No examples provided.
weave_list List woven folders ~23
List the folders this server has indexed, with their file and passage counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
weave_search Search the weave ~101
Search the woven folders in plain language: where something is defined, handled, configured or explained. Returns the nearest passages with their file, line range and centred-cosine score. Use it before grep when you do not know the identifier or file name.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Search only this woven folder |
| k | integer | – | How many passages (default 8) |
| query | string | yes | What to find, in plain words or code |
No output schema declared.
No examples provided.
How do I install the Sunstone Weave: Local Semantic Code Search MCP server?
Sunstone Weave: Local Semantic Code Search runs locally as an npm package, launched with npx -y blackwindow-weave-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 · blackwindow-weave-mcp
claude mcp add space-bacon-blackwindow-weave-mcp -- npx -y blackwindow-weave-mcp
What is the Sunstone Weave: Local Semantic Code Search MCP server?
Sunstone Weave: Local Semantic Code Search is an MCP server listed in the public MCP registry as io.github.space-bacon/blackwindow-weave-mcp. Semantic search over local folders of code and docs, with a code-search encoder running on your CPU. This page covers its npm package (blackwindow-weave-mcp).
Is the Sunstone Weave: Local Semantic Code Search MCP server safe to use?
Sunstone Weave: Local Semantic Code Search scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 24 October 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 Sunstone Weave: Local Semantic Code Search MCP server expose?
Sunstone Weave: Local Semantic Code Search exposes 4 tools: weave_folder, weave_search, weave_list, weave_forget. Their descriptions and schemas cost roughly 275 tokens of context every time the server is loaded.
Is the Sunstone Weave: Local Semantic Code Search MCP server still maintained?
Sunstone Weave: Local Semantic Code Search is still listed as active in the MCP registry. We last reached this channel on 24 October 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 Sunstone Weave: Local Semantic Code Search MCP server under?
Sunstone Weave: Local Semantic Code Search declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.