io.github.Weavatrix/weavatrix-refactor
NPM · WEAVATRIX-REFACTOR · SCANNED SEP 20
Transactional refactoring extension with 11 evidence-backed tools, previews, and rollback.
Available components
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Weavatrix/weavatrix-refactor). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 26 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1368 tokens (~124/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "organize_imports" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.Weavatrix/weavatrix-refactor MCP server?
io.github.Weavatrix/weavatrix-refactor runs locally as an npm package, launched with npx -y weavatrix-refactor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · weavatrix-refactor
claude mcp add weavatrix-weavatrix-refactor -- npx -y weavatrix-refactor
{
"mcpServers": {
"weavatrix-weavatrix-refactor": {
"command": "npx",
"args": [
"-y",
"weavatrix-refactor"
]
}
}
} {
"servers": {
"weavatrix-weavatrix-refactor": {
"command": "npx",
"args": [
"-y",
"weavatrix-refactor"
]
}
}
} codex mcp add weavatrix-weavatrix-refactor -- npx -y weavatrix-refactor
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"weavatrix-weavatrix-refactor": {
"type": "local",
"command": [
"npx",
"-y",
"weavatrix-refactor"
],
"enabled": true
}
}
} openclaw mcp add weavatrix-weavatrix-refactor --command npx --arg -y --arg weavatrix-refactor
mcp_servers:
weavatrix-weavatrix-refactor:
command: "npx"
args: ["-y", "weavatrix-refactor"] {
"McpServers": {
"weavatrix-weavatrix-refactor": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"weavatrix-refactor"
]
}
}
} assistant mcp add weavatrix-weavatrix-refactor -t stdio -c npx -a -y weavatrix-refactor
{
"mcpServers": {
"weavatrix-weavatrix-refactor": {
"command": "npx",
"args": [
"-y",
"weavatrix-refactor"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 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.
- 11 Sept 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.
- 9 Sept 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.
- 7 Sept 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.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/weavatrix-refactor@1.0.11
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Weavatrix/weavatrix-refactor |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Weavatrix/weavatrix-refactor/.github/workflows/npm-release.yml@refs/tags/v1.0.11 |
| Rekor log index | 2580793333 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4a8c57218cf9076402cff28763104d488a6197641ae3889a83ef30737a766734a71bc705fed91a76568c5234e2cd2c4f9bb9675eb749c6d0256aa8147 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
apply_edit_plan ~206
Apply a weavatrix.edit-plan.v1 envelope (from a weavatrix-refactor-js plan producer or weavatrix-online plan_refactor) to the active repository. mode="preview" (default) verifies hashes and before-texts and issues a single-use confirm_token; mode="apply" consumes the token and writes atomically with an automatic rollback bundle. Requires WEAVATRIX_ALLOW_SOURCE_EDITS=1 to write. Only EXACT_LSP/RESOLVED/EXTRACTED/LEXICAL_EXACT edits are ever applied; uncertain references are reported, never guessed.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_token | string | – | Required for mode="apply"; issued by the preview step, single-use, 5-minute TTL |
| mode | string | – | – |
| output_format | string | – | text returns concise TextContent; json also returns the stable structuredContent envelope |
| plan | object | yes | The weavatrix.edit-plan.v1 envelope, verbatim as produced by the planning tool |
No output schema declared.
No examples provided.
bulk_replace ~119
Two-stage occurrence-selective pattern replace over the indexed universe. Preview (no selection) returns stable occurrence ids; then pass occurrence_ids or expected_count to plan. literal:true by default.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_count | integer | – | – |
| flags | string | – | – |
| literal | boolean | – | – |
| occurrence_ids | array | – | – |
| output_format | string | – | text returns concise TextContent; json also returns the stable structuredContent envelope |
| path_prefix | string | – | – |
| pattern | string | yes | – |
| replacement | string | yes | – |
No output schema declared.
No examples provided.
change_signature ~106
Add or remove a function/method parameter (JS/TS) with byte-exact call-site argument surgery. Always PARTIAL (call sites from graph edges); spread/value-add reported UNCERTAIN. operation: {kind:"add_parameter",name,default?} | {kind:"remove_parameter",index}.
| Name | Type | Req | Description |
|---|---|---|---|
| operation | object | yes | – |
| output_format | string | – | text returns concise TextContent; json also returns the stable structuredContent envelope |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
delete_readiness ~87
Per-symbol deletion verdict {safe: true|false|UNPROVEN, knownReferences, unknownDynamicUsages, confidence, reason} plus the deletion span. Exported symbols cap at UNPROVEN; always REVIEW_REQUIRED, never auto-delete.
| Name | Type | Req | Description |
|---|---|---|---|
| output_format | string | – | text returns concise TextContent; json also returns the stable structuredContent envelope |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
edit_symbol ~86
Symbol-anchored edit over the parser source range (all languages): replace_symbol_body | insert_before_symbol | insert_after_symbol. JS/TS results are parse-gated.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| operation | string | yes | – |
| output_format | string | – | text returns concise TextContent; json also returns the stable structuredContent envelope |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
move_file ~103
Relocate a JS/TS file: rewrites the moved file own imports and every importer specifier, and reports the architecture dry-run (WOULD_VIOLATE/WOULD_IMPROVE). A review plan the agent applies (it renames a file), not an apply envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| output_format | string | – | text returns concise TextContent; json also returns the stable structuredContent envelope |
| to | string | yes | – |
No output schema declared.
No examples provided.
move_symbol ~91
Dry-run for moving a declaration to another file: predicts introduced/removed runtime cycles and architecture violations plus the blast radius. PROJECTED from graph edges — no byte-exact edits; apply the mechanical move yourself and run verified_change.
| Name | Type | Req | Description |
|---|---|---|---|
| output_format | string | – | text returns concise TextContent; json also returns the stable structuredContent envelope |
| symbol | string | yes | – |
| to_file | string | yes | – |
No output schema declared.
No examples provided.
organize_imports ~85
Removes provably-unused named imports from a JS/TS file (a binding is removed only when its name occurs once in the file). Default/namespace imports are reported UNCERTAIN, never removed; sorting is left to the formatter.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | – |
| output_format | string | – | text returns concise TextContent; json also returns the stable structuredContent envelope |
No output schema declared.
No examples provided.
rename_related_symbols ~155
Complete coordinated JS/TS multi-symbol rename as ONE atomic workflow with conflict/chain/swap detection. Default mode="preview" returns a plan-bound confirm_token; repeat with identical renames, mode="apply", and that token to write atomically with rollback. Blocks entirely if any sub-rename fails.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_token | string | – | Required for mode="apply"; single-use and bound to the exact generated plan and working tree |
| mode | string | – | preview verifies the generated plan and returns a confirm_token; apply recomputes the same plan and consumes that token |
| output_format | string | – | text returns concise TextContent; json also returns the stable structuredContent envelope |
| renames | array | yes | – |
No output schema declared.
No examples provided.
rename_symbol ~201
Complete cross-language rename workflow: EXACT LSP backend for JS/TS, SQL schema backend for .sql, graph+lexical backend for Rust/Python/Go/Java/C#/Solidity. Default mode="preview" proves the byte-exact edits and returns a single-use confirm_token; repeat the same call with mode="apply" and that token for an atomic write with rollback. Requires WEAVATRIX_ALLOW_SOURCE_EDITS=1 only for apply.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_token | string | – | Required for mode="apply"; single-use and bound to the exact generated plan and working tree |
| mode | string | – | preview verifies the generated plan and returns a confirm_token; apply recomputes the same plan and consumes that token |
| new_name | string | yes | – |
| output_format | string | – | text returns concise TextContent; json also returns the stable structuredContent envelope |
| symbol | string | yes | Exact symbol id (file#name@line) |
No output schema declared.
No examples provided.
rollback_last_apply ~81
Restore the repository files from the most recent apply_edit_plan rollback bundle. All-or-nothing: if any target file changed after the apply, nothing is restored and the drifted files are reported. Requires WEAVATRIX_ALLOW_SOURCE_EDITS=1.
| Name | Type | Req | Description |
|---|---|---|---|
| output_format | string | – | text returns concise TextContent; json also returns the stable structuredContent envelope |
No output schema declared.
No examples provided.
What is the io.github.Weavatrix/weavatrix-refactor MCP server?
io.github.Weavatrix/weavatrix-refactor is an MCP server listed in the public MCP registry as io.github.Weavatrix/weavatrix-refactor. Transactional refactoring extension with 11 evidence-backed tools, previews, and rollback. This page covers its npm package (weavatrix-refactor).
Is the io.github.Weavatrix/weavatrix-refactor MCP server safe to use?
io.github.Weavatrix/weavatrix-refactor scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.Weavatrix/weavatrix-refactor MCP server expose?
io.github.Weavatrix/weavatrix-refactor exposes 11 tools: rename_symbol, rename_related_symbols, apply_edit_plan, rollback_last_apply, change_signature, and 6 more. Their descriptions and schemas cost roughly 1,320 tokens of context every time the server is loaded.
Is the io.github.Weavatrix/weavatrix-refactor MCP server still maintained?
io.github.Weavatrix/weavatrix-refactor is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.Weavatrix/weavatrix-refactor MCP server under?
io.github.Weavatrix/weavatrix-refactor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.