Weavatrix Online

Take repository intelligence across a network without handing the network your repository.

The explicit network boundary of the Weavatrix ecosystem. Core and Refactor remain separate installs.

Weavatrix Online is the MIT-licensed MCP connector for Weavatrix Cloud and compatible customer-controlled endpoints. It keeps analysis local, produces an inspectable source-free payload, and requires an exact short-lived confirmation before that payload can leave the machine.

The public Online profile exposes 7 MCP tools for endpoint discovery, advisories, malware review, architecture contracts, and controlled synchronization. The local weavatrix-js graph engine is an implementation detail: its tools are not re-exported, so installing Core, Refactor, and Online together does not duplicate their catalogs in an agent's context.

Installing or starting Online does not synchronize anything. preview_sync makes no network request; sync_graph accepts only the still-valid preview for the same repository, destination, payload, and graph.

Choose the right Weavatrix package

Online currently uses the JavaScript graph/runtime package internally:

weavatrix-online 0.3.4
  └─ weavatrix-js 0.3.x (internal; no Core tools re-exported)

It does not proxy the native weavatrix executable, import weavatrix-refactor, or copy either engine. Use weavatrix when the graph must remain entirely local. Use weavatrix-online when endpoint status, remotely managed architecture contracts, advisory refresh, or explicit source-free synchronization is part of the workflow.

Install and run

Plugins for Cursor, Codex, Claude, and Grok

The repository now contains one portable plugin bundle at plugins/weavatrix-online plus native marketplace manifests for all four clients. The plugin starts the pinned npm release and includes an optional, compact skill with one lazily loaded card per Online method.

codex plugin marketplace add Weavatrix/weavatrix-online --sparse .agents/plugins plugins/weavatrix-online
codex plugin add weavatrix-online@weavatrix-online

claude plugin marketplace add Weavatrix/weavatrix-online --sparse .claude-plugin plugins
claude plugin install weavatrix-online@weavatrix-online

grok plugin marketplace add Weavatrix/weavatrix-online

Cursor can load the bundle locally from ~/.cursor/plugins/local/weavatrix-online; public marketplace discovery starts after the listing is reviewed and approved.

Direct MCP launch

Run the pinned release without a global install:

npx -y weavatrix-online@0.3.4 C:\path\to\repository

The command starts a stdio MCP server. The first positional argument is the repository to analyze. An existing graph can be supplied explicitly:

npx -y weavatrix-online@0.3.4 C:\graphs\repository\graph.json C:\path\to\repository

The npm package is intentionally an executable MCP product; it does not advertise a nonexistent JavaScript library entry point.

Codex

[mcp_servers.weavatrix_online]
command = "npx"
args = ["-y", "weavatrix-online@0.3.4", "C:\\path\\to\\repository"]

[mcp_servers.weavatrix_online.env]
WEAVATRIX_SYNC_URL = "https://app.weavatrix.com/api/v1/graphs/sync"
WEAVATRIX_SYNC_TOKEN = "load-from-runtime-secret-storage"

Claude Desktop

{
  "mcpServers": {
    "weavatrix-online": {
      "command": "npx",
      "args": [
        "-y",
        "weavatrix-online@0.3.4",
        "C:\\path\\to\\repository"
      ],
      "env": {
        "WEAVATRIX_SYNC_URL": "https://app.weavatrix.com/api/v1/graphs/sync",
        "WEAVATRIX_SYNC_TOKEN": "load-from-runtime-secret-storage"
      }
    }
  }
}

Keep bearer tokens in the MCP client's runtime secret storage. Do not put them in Git, a committed .env, release logs, or checked-in MCP configuration.

The seven Online tools

Install Weavatrix Core for read-only repository intelligence and Weavatrix Refactor for guarded source changes. Their methods remain in their owning products.

Typical workflows

Check endpoint compatibility before doing any repository work:

{"name":"online_status","arguments":{"timeout_ms":10000}}

Refresh advisory evidence, then evaluate it locally:

{"name":"refresh_advisories","arguments":{"timeout_ms":20000}}
{"name":"scan_dependency_vulnerabilities","arguments":{"max_age_days":30}}

Review the exact upload without sending it:

{"name":"preview_sync","arguments":{"payload_version":3}}

After a human or trusted controller approves the displayed destination, section summary, counts, size, and body hash, use the returned token:

{
  "name": "sync_graph",
  "arguments": {
    "payload_version": 3,
    "dry_run": false,
    "confirm_token": "token-returned-by-preview_sync",
    "timeout_ms": 30000
  }
}

Changing the graph, repository, destination, payload, or expiry state invalidates that approval. A rejected or unavailable endpoint leaves the graph local.

Network and consent boundary

local repository
      │
      ▼
local graph + derived evidence
      │
      ▼
preview_sync ── inspect destination, sections, counts, size, and SHA-256
      │
      ▼
explicit approval
      │
      ▼
sync_graph ── capability negotiation ── approved endpoint

The connector enforces:

• HTTPS for every non-loopback destination;
• loopback-only HTTP for local development;
• no credentials embedded in URLs;
• endpoint capability negotiation before upload;
• a bounded versioned payload allowlist;
• exact preview hashing and a short-lived confirmation token;
• honest NOT_CHECKED and PARTIAL states when evidence is incomplete.

The sync payload contains bounded graph topology and selected derived evidence. It excludes source bodies, snippets, absolute host paths, environment values, credentials, Git remotes, and fields outside the wire allowlist. “Source-free” does not mean anonymous: review the displayed repository identity, destination, counts, sections, and hash before approval.

Configuration

Compatible endpoints must implement the versioned capability and sync contracts. Capability discovery itself sends no repository evidence.

Security evidence without false certainty

Advisory refresh covers pinned npm, PyPI, Go, Maven/Gradle, and crates.io coordinates found in bounded repository manifests. A clean zero is allowed only when the current inventory matches a complete, current Online cache.

Malware review is static and bounded. It can identify evidence such as download-and-execute lifecycle scripts, reverse-shell patterns, decoded execution, miner indicators, credential-file reads, or suspicious exfiltration endpoints. It cannot prove execution, provenance, credential exposure, safety, or compromise.

Architecture contracts are validated locally before becoming active.

Report vulnerabilities privately through GitHub Security Advisories.

Architecture

The connector is a strict modular ports-and-adapters system:

policy
  └─ discovery adapters
       └─ security cache and evidence services
            └─ Online actions
                 └─ MCP composition and executable

• policy: destination validation, version matching, inventory identities, and malware evidence rules;
• discovery: bounded manifest and installed-package adapters;
• security: atomic advisory state, cached matching, scanning, and reporting;
• online-actions: capability, contract, advisory, preview, and sync use cases;
• composition: extension registration, launcher, and stdio executable.

The checked-in architecture contract enforces zero runtime cycles, production files at or below 300 physical lines, and functions at or below 100 physical lines, with no exceptions and no violation baseline.

Development and release proof

npm ci --ignore-scripts
npm test
npm run verify:release
npm audit
npm pack --dry-run --json

The release gate verifies package identity, dependency ranges, exact installed versions, MCP Registry metadata, checked-in release notes, MIT licensing, the published file allowlist, and tag/version agreement. CI repeats the tests, security audit, and package dry-run on Node.js 24.

License

MIT. Weavatrix Online and its internal weavatrix-js runtime are independently versioned MIT-licensed packages.