# io.github.Weavatrix/weavatrix-refactor (npm · weavatrix-refactor)

Transactional refactoring extension with 11 evidence-backed tools, previews, and rollback.

- Trust score: 89/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `weavatrix-refactor`: 89/100 (this document), [markdown](https://verifymcp.io/servers/weavatrix-weavatrix-refactor/weavatrix-refactor.md), [page](https://verifymcp.io/servers/weavatrix-weavatrix-refactor/weavatrix-refactor)

## Channel facts

- Registry: `npm`
- Package: `weavatrix-refactor`
- Version: `1.0.11`
- 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-09-20.

- **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 Weavatrix/weavatrix-refactor).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 26 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 46% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add weavatrix-weavatrix-refactor -- npx -y weavatrix-refactor
```

### Cursor

```json
{
  "mcpServers": {
    "weavatrix-weavatrix-refactor": {
      "command": "npx",
      "args": [
        "-y",
        "weavatrix-refactor"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "weavatrix-weavatrix-refactor": {
      "command": "npx",
      "args": [
        "-y",
        "weavatrix-refactor"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add weavatrix-weavatrix-refactor -- npx -y weavatrix-refactor
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add weavatrix-weavatrix-refactor --command npx --arg -y --arg weavatrix-refactor
```

### Hermes

```yaml
mcp_servers:
  weavatrix-weavatrix-refactor:
    command: "npx"
    args: ["-y", "weavatrix-refactor"]
```

### Netclaw

```json
{
  "McpServers": {
    "weavatrix-weavatrix-refactor": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "weavatrix-refactor"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add weavatrix-weavatrix-refactor -t stdio -c npx -a -y weavatrix-refactor
```

### Other

```json
{
  "mcpServers": {
    "weavatrix-weavatrix-refactor": {
      "command": "npx",
      "args": [
        "-y",
        "weavatrix-refactor"
      ]
    }
  }
}
```

## 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-09-20 (score 89, +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.

### 2026-09-18 (score 88, +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.

### 2026-09-16 (score 87, +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.

### 2026-09-13 (score 86, +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.

### 2026-09-11 (score 85, +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.

### 2026-09-09 (score 84, +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-09-07 (score 83, +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-09-05 (score 82, +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.

## MCP tools (11)

### `rename_symbol` (~201 tokens)

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.

Input parameters:

- `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, required)
- `output_format` (string): text returns concise TextContent; json also returns the stable structuredContent envelope
- `symbol` (string, required): Exact symbol id (file#name@line)

### `rename_related_symbols` (~155 tokens)

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.

Input parameters:

- `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, required)

### `apply_edit_plan` (~206 tokens)

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.

Input parameters:

- `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, required): The weavatrix.edit-plan.v1 envelope, verbatim as produced by the planning tool

### `rollback_last_apply` (~81 tokens)

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.

Input parameters:

- `output_format` (string): text returns concise TextContent; json also returns the stable structuredContent envelope

### `change_signature` (~106 tokens)

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}.

Input parameters:

- `operation` (object, required)
- `output_format` (string): text returns concise TextContent; json also returns the stable structuredContent envelope
- `symbol` (string, required)

### `edit_symbol` (~86 tokens)

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.

Input parameters:

- `content` (string, required)
- `operation` (string, required)
- `output_format` (string): text returns concise TextContent; json also returns the stable structuredContent envelope
- `symbol` (string, required)

### `bulk_replace` (~119 tokens)

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.

Input parameters:

- `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, required)
- `replacement` (string, required)

### `organize_imports` (~85 tokens)

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.

Input parameters:

- `file` (string, required)
- `output_format` (string): text returns concise TextContent; json also returns the stable structuredContent envelope

### `move_file` (~103 tokens)

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.

Input parameters:

- `from` (string, required)
- `output_format` (string): text returns concise TextContent; json also returns the stable structuredContent envelope
- `to` (string, required)

### `move_symbol` (~91 tokens)

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.

Input parameters:

- `output_format` (string): text returns concise TextContent; json also returns the stable structuredContent envelope
- `symbol` (string, required)
- `to_file` (string, required)

### `delete_readiness` (~87 tokens)

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.

Input parameters:

- `output_format` (string): text returns concise TextContent; json also returns the stable structuredContent envelope
- `symbol` (string, required)

## Diagnostics

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

## Score history

- 2026-09-20: 89
- 2026-09-19: 88
- 2026-09-18: 88
- 2026-09-17: 87
- 2026-09-16: 87
- 2026-09-15: 86
- 2026-09-14: 86
- 2026-09-13: 86
- 2026-09-12: 85
- 2026-09-11: 85
- 2026-09-10: 84
- 2026-09-09: 84
- 2026-09-08: 83
- 2026-09-07: 83
- 2026-09-06: 82
- 2026-09-05: 82
- 2026-09-04: 81
- 2026-09-03: 81
- 2026-09-02: 80
- 2026-09-01: 80
- 2026-08-31: 76
- 2026-08-30: 76
- 2026-08-29: 76
- 2026-08-28: 76
- 2026-08-27: 76
- 2026-08-26: 76
- 2026-08-25: 76
- 2026-08-24: 50

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/weavatrix-refactor
- Socket report: https://socket.dev/npm/package/weavatrix-refactor
- Repository: https://github.com/Weavatrix/weavatrix-refactor
- Website: https://weavatrix.com/
- Changelog RSS feed: https://verifymcp.io/servers/weavatrix-weavatrix-refactor/weavatrix-refactor.xml
- Changelog JSON feed: https://verifymcp.io/servers/weavatrix-weavatrix-refactor/weavatrix-refactor.json
- HTML version of this page: https://verifymcp.io/servers/weavatrix-weavatrix-refactor/weavatrix-refactor