Weavatrix Js vs Forensic Deepdive

In-depth architectural comparison of the Weavatrix Js and Forensic Deepdive MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Weavatrix Js when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Weavatrix Js Details

Choose Forensic Deepdive when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Forensic Deepdive Details

Feature & Specification Comparison

Specification	Weavatrix Js Developer Tools	Forensic Deepdive Developer Tools
Summary	Always-fresh local repo graph: LSP-backed impact, Health, dead code, endpoints, architecture.	Persistent code knowledge graph + 9 composite MCP tools for AI coding agents.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "weavatrix-js": {
      "command": "npx",
      "args": [
        "-y",
        "weavatrix-js"
      ]
    }
  }
}

{
  "mcpServers": {
    "forensic-deepdive": {
      "command": "uvx",
      "args": [
        "uv"
      ]
    }
  }
}

Related MCP Server Comparisons