Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Weavatrix/weavatrix-refactorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/weavatrix/weavatrix-refactor/weavatrix-refactor-weavatrix-refactor)<a href="https://agentmods.dev/mcp/weavatrix/weavatrix-refactor/weavatrix-refactor-weavatrix-refactor"><img src="https://agentmods.dev/badge/mcp/weavatrix/weavatrix-refactor/weavatrix-refactor-weavatrix-refactor.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
weavatrix-refactor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"weavatrix-refactor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]",
"mcp",
".",
"--profile=refactor"
],
"env": {
"WEAVATRIX_ALLOW_SOURCE_EDITS": "1"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 16 lines scan A c3f370033449
weavatrix-refactor is an MCP server published in the GitHub repository Weavatrix/weavatrix-refactor (1 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
weavatrix-refactor-js
Transactional refactoring MCP with 11 evidence-backed tools, hash-bound previews, and rollback. Runs locally from the weavatrix-refactor-js npm package. Needs 3 environment variables to run.
weavatrix-online
Weavatrix Online extension: guarded sync, advisories, malware review, architecture contracts. Runs locally from the weavatrix-online npm package. Needs 6 environment variables to run.
weavatrix-online
Extension-only Weavatrix MCP for preview-gated graph sync, advisories, malware review, and remote architecture contracts. Runs locally from the weavatrix-online npm package.
weavatrix-js
JavaScript engine of Weavatrix, the local repository intelligence MCP for AI coding agents: an always-fresh architecture graph with production-first evidence — blast radius, dead code, endpoints, clones, history, Health and architecture safeguards, with h. Runs locally from the weavatrix-js npm package. Needs 3…
ts-mcp-server
MCP server that renames/moves TypeScript files and updates all imports via tsserver. Runs locally from the ts-mcp-server npm package.
revise-mcp
Tools to revise and refactor code via MCP. Runs locally from the revise-mcp Python package.