MCP.Market

Weavatrix Js MCP server

by sergii-ziborov·io.github.sergii-ziborov/weavatrix-js·v0.3.15

Always-fresh local repo graph: LSP-backed impact, Health, dead code, endpoints, architecture.

A89/100grade A
What users say
No reviews yet
Be the first
Safety scan
A89/100

full report

Adoption
Growing

0 stars64 downloads/wk

Reviews

Write one

Nobody has reviewed Weavatrix Js yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Weavatrix Js tools (34, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • change_impact

    Verdict-first, symbol-aware blast radius. Parses a zero-context git diff and uses one bounded EXACT_LSP batch query for direct references to changed JavaScript/TypeScript symbols; transitive hops stay explicitly graph-backed. Additive exports do not inherit legacy file importers. Measured coverage is used when present; otherwise static reachability is labelled, not treated as coverage.

  • context_bundle

    Return one compact, bounded source bundle for an exact symbol: definition, production-first inbound/outbound containers, exact re-export sites, on-demand TS/JS reference evidence and diverse excerpts around call sites. Use before an edit when query_graph would be too broad.

  • coverage_map

    Map a real existing coverage report onto the graph. If no report exists, return clearly labelled static test reachability (a test imports/reaches a source file) with actualCoverage=NOT_AVAILABLE; reachability is never presented as measured coverage.

  • explain_architecture_violation

    Explain one active architecture violation and the governing rule.

  • find_dead_code

    Conservative review queue for statically unreferenced files, functions, methods and symbols. Returns confidence, reason, bounded evidence and explicit framework/dynamic/reflection/public-API caveats; never an auto-delete verdict. Tests, generated/vendored code, mocks, stories, docs, benchmarks and temporary roots are excluded by default.

  • find_duplicates

    Content-based clone detection over production code (MOSS winnowing over method bodies). Supports high-confidence small clones down to 12 tokens when min_tokens is lowered. Tests, classified non-product paths, all-router framework boilerplate and immutable declarative catalogs are excluded by default; opt them in explicitly.

  • get_architecture_contract

    Read the owner-approved architecture target or safely bootstrap one. With action=preview, returns an adaptive candidate, observed-but-not-enforced dependency directions, verification, exact file content/hash and a short-lived confirmation token. action=approve creates the local contract only after explicit token confirmation and never overwrites an active target.

  • get_community

    Get all nodes in a community by community ID (0-indexed by size).

  • get_dependents

    Transitive blast-radius of ONE node. JavaScript/TypeScript symbols use a cached on-demand EXACT_LSP point query by default, then traverse exact direct callers through the wider graph; incomplete precision is labelled and never silently presented as exact. Set precision=graph to skip LSP or include_container_importers for a conservative module-wide radius.

  • get_neighbors

    Get all direct neighbors of a node with edge details (1 hop, call sites deduped). For transitive impact use get_dependents; for the impact of your current branch changes use change_impact.

  • get_node

    Get full details for a specific node by label or ID.

  • git_history

    Behavioral architecture evidence from bounded local git history: churn × connectivity hotspots, hidden co-change coupling, and expected test/source coupling. Reads numstat only — never commit messages, authors, or source bodies.

  • god_nodes

    Rank production-code connectivity hubs by unique call/import/reference neighbors, with class/method ownership reported separately from runtime connectivity. Repeated call sites do not inflate the rank; classified tests, generated/build output and other non-product paths are excluded by default.

  • graph_diff

    Structural graph diff: compare the current graph with an immutable Git-ref baseline (base_ref such as HEAD~1 or main), or with graph.prev.json from the last rebuild when base_ref is omitted. Reports architecture drift, cycle changes and symbols that lost their last caller.

  • graph_stats

    Return summary statistics: node count, edge count, communities, versioned edge-provenance/legacy-confidence breakdowns, and graph build time vs repo HEAD (staleness).

  • hot_path_review

    Rank a focused production-symbol hot-path queue from parser-derived local complexity, inside-loop allocations/copies/scans/sorts/recursion, graph fan-in/fan-out, and measured coverage or clearly labelled static test reachability. The default score gate is 85 with a narrow strong-local fallback; set min_score=0 for the full diagnostic queue. This is not profiler data or interprocedural Big-O.

  • inspect_symbol

    Inspect one exact symbol with an on-demand TypeScript/JavaScript LSP reference query, grouped occurrence containers, graph blast radius, complexity facts and bounded local source context. Ambiguous labels fail closed; point queries never replace the broad precision overlay.

  • list_communities

    List graph communities named by their dominant folder (largest first) with sample files — a readable module overview; feed the list position into get_community.

  • list_endpoints

    Inventory of HTTP endpoints defined in the repo (Express/Fastify/Nest/Flask/FastAPI/Go mux/Rust axum and actix-web/Spring MVC and WebFlux): declared and reachable composed paths, static mount provenance, confidence, handler, file:line, and Spring conditional/default-active state.

  • list_known_repos

    OFFLINE RETARGET: list every registered local repository graph from the global per-user registry, regardless of parent folder.

  • module_map

    First orientation view for understanding an unfamiliar application with little context: a production-first folder architecture map with file/symbol counts and strongest module dependencies, separating runtime, TypeScript type-only and language compile-only coupling.

  • open_repo

    OFFLINE RETARGET: switch this server to another local Git repository, building its graph when missing. This explicit tool call changes the active repository boundary; pass build:false to probe without building. Omitted mode/precision preserve an existing graph; a new graph uses full and the startup precision setting (lsp unless WEAVATRIX_PRECISION=off). Omit the retarget capability at registration

  • prepare_change

    Select active target-architecture rules for an intended set of changed files. Run before a non-trivial edit.

  • propose_architecture_exception

    Prepare, but never apply, a bounded exception proposal for human review.

  • query_graph

    Explore a focused production-first graph around a concept or exact symbols (BFS/DFS). Exact seed files/symbols stay pinned; relation_filter and flow_direction support bounded event/data-flow views without a separate tool. Classified paths and unreferenced constant/field leaves stay suppressed unless explicitly requested.

  • read_source

    Read the actual source of a node (by label/ID) or a repo-relative file path — the symbol's lines with context. The graph stores only locations, not source text. For a path read, pass start_line to anchor the window anywhere in the file (otherwise it shows the head).

  • rebuild_graph

    Rebuild the active full-repository graph and report a structural delta. Omitted mode/precision preserve the active graph; a first build uses full and the startup precision setting (lsp unless WEAVATRIX_PRECISION=off). The local TypeScript/JavaScript LSP overlay validates bounded ambiguous edges; precision:off is an explicit fallback. With scope, build an isolated diagnostic graph without replacing

  • run_auditwrite action

    Offline production-first repository Health review for structure, dependency declarations and lockfile integrity, bounded runtime-correctness/concurrency patterns, dead code and coverage. Vulnerability advisory matching and installed-dependency malware heuristics are separate explicit weavatrix-online tools. Unsupported Maven/Gradle import verification is NOT_SUPPORTED/PARTIAL, never a clean zero.

  • search_code

    Full-text or regex search across the repo source (ripgrep-backed, Node fallback). The graph only stores structure — use this to find literal text/patterns, then get_node/get_neighbors for structure.

  • shortest_path

    Find the shortest path between two concepts in the knowledge graph.

  • trace_api_contract

    Cross-repository HTTP, GraphQL, gRPC and event/topic contract, handler-liveness and blast-radius evidence. Joins static models with optional revision-bound runtime/OTLP evidence; unobserved dynamic URLs/topics/reflection remain explicit UNKNOWN. Medium/high-confidence external matches mark a handler/contract NOT_DEAD_EXTERNAL_USE. Repository paths stay local and runtime report paths are repository

  • trace_endpoint

    Resolve one exact reachable HTTP endpoint, prove its router mount chain, bind its handler symbol, and return a bounded production-only multi-hop call graph with call-site excerpts. This is a focused projection of the repository graph, not text-search inference.

  • verified_change

    Pre-commit, proof-carrying change safeguard. Given a natural-language task and current diff/files, returns compact edit contexts, bounded call-argument data-flow, blast radius, graph/architecture/duplicate/API ratchets, affected tests, and one PASS/BLOCKED/UNKNOWN verdict. Use this high-level workflow before manually composing lower-level checks. Package tests run only when explicitly requested an

  • verify_architecture

    Verify the fresh graph against the active target contract and ratchet; separates new, existing, fixed and excepted debt.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan257 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 31 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Weavatrix Js compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
89/100
higher than 80% of 48,255 servers
Tools
34
the typical server has 7
Tools that change things
3%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
64
more than 51% of 12,191 servers with a package

What its tools let an agent do: 32 read · 1 create · 1 run or deploy

Install Weavatrix Js in Claude Code, Cursor or VS Code

Runs npx -y weavatrix-js on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add weavatrix-js -- npx -y weavatrix-js
Add to Cursor

What the publisher says

From the Weavatrix Js repository's README, as published. We do not edit it. Read it on GitHub

Weavatrix JS

Part of the Weavatrix ecosystem. This repository preserves the explicit JavaScript engine line.

This is the JavaScript engine of Weavatrix, continued as weavatrix-js.

The weavatrix npm package ships

the native Rust engine from

weavatrix-rust starting

with 1.0.0; pin weavatrix@0.3.14 or install weavatrix-js to stay on the

JavaScript implementation (including its LSP-assisted TypeScript path).

Local repository intelligence for AI coding agents — understand an application fast, then change it with evidence.

Weavatrix builds a reusable living graph of any local repository — files, symbols, imports, calls, inheritance, Health findings, clone families and Git-history coupling — and gives Claude Code, Codex or any MCP client a bounded map for fast understanding and low repeated context. The same graph then answers change impact, Health, dead-code review, duplicates, history and intended-architecture questions. 34 network-free tools. No repository data leaves your machine.

  • Website: weavatrix.com
  • Source: github.com/Weavatrix/weavatrix-js
  • npm: weavatrix-js — npx -y weavatrix-js

Primary native Rust engine

weavatrix-rust is the pure-Rust read-only MCP and library implementation. Its default build exposes 39 tools, covers the 34 read-only capabilities of this JavaScript line and adds cross-repository Git, vector search, semantic/SEO linking, and temporal-memory context through independent MIT crates.

cargo install weavatrix-rust
weavatrix mcp <repoRoot> --profile=code

The Rust engine does not invoke git, rg, Node.js, Python, a language server, or code from the analyzed repository. Use --profile=all, code, or seo to expose one bounded view without running duplicate MCP servers. Same-revision benchmarks and limitations are published in its benchmark report.

This package is the complete offline engine under the MIT license: it reads and analyzes your code, initiates no outbound HTTP, and never edits your source. It is the read-only base of a layered stack — add weavatrix-refactor (Apache-2.0) to apply hash-verified, reversible edits, or weavatrix-online for authorized Cloud or self-hosted sync. Each is an optional superset that depends on this core through a supported extension API; the offline/online split is documented in docs/adr/0001-v0.3-offline-online-split.md.

Install

Requires Node ≥ 18.

# Claude Code
claude mcp add -s user weavatrix-js -- npx -y weavatrix-js <repoRoot>

# Codex CLI
codex mcp add weavatrix-js -- npx -y weavatrix-js <repoRoot>
# or in ~/.codex/config.toml
[mcp_servers.weavatrix-js]
command = "npx"
args = ["-y", "weavatrix-js", "C:/path/to/repo"]
startup_timeout_sec = 20
tool_timeout_sec = 60

Or run from a clone:

git clone https://github.com/Weavatrix/weavatrix-js
cd weavatrix-js && npm install
claude mcp add -s user weavatrix-js -- node <path-to>/weavatrix-js/bin/weavatrix-mcp.mjs <repoRoot>

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Weavatrix Js: common questions

Is Weavatrix Js MCP server safe?
Yes, by our scan: it is graded A (89/100). Read the Weavatrix Js safety report
How do I install Weavatrix Js?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Weavatrix Js need an API key?
No secret keys are declared. It reads 3 settings from the environment.
Is Weavatrix Js maintained?
The last commit was 71 days ago (2026-08-24). The latest release is v0.3.15.
What can I use instead of Weavatrix Js?
Servers from other publishers that do the same job: pyscn MCP server.
How does Weavatrix Js compare with other MCP servers?
safety score 89/100 (higher than 80% of 48,255 servers); tools 34 (the typical server has 7); tools that change things 3% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Weavatrix Js

Same job from other publishers: the closest match first, then the best rated.

  • pyscn
    Python code analysis for AI agents: complexity, dead code, clones, coupling, and a health score.
    A