ToolScope v0.3.1: offline comparison kit

Compare two saved ToolScope exports with Node.js 24. The offline kit includes the command, synthetic examples, licenses and a source/hash manifest. No clone, npm install, server or browser is needed.

Download ToolScope-v0.3.1-offline-kit.zip, verify it against SHA256SUMS, extract it and run this from the extracted directory:

node scripts/compare-tool-baselines.mjs examples/tool-baselines/before.json examples/tool-baselines/after.json

The example intentionally exits 1: inspect_part was added and lookup.description changed. Compare before.json with itself for exit 0. Invalid inputs return 2, with an explanation on stderr.

For your own exports:

node scripts/compare-tool-baselines.mjs baseline.json current.json

The kit bundles the existing command and shared validator. It preserves both inputs, requires the same catalog server identity and reports definition changes. It does not connect to the server, call tools, determine backward compatibility or authenticate the files' history. Walkthrough and format limits.

The source archives contain the full application, which still needs its documented dependency installation. This is an independent MCP Inspector derivative with attribution and original license terms retained. GitHub release version 0.3.1 is separate from the inherited private package version 2.8.0; nothing is published to npm.

Verification: all 370 script tests and the exact-commit PR/branch validation, four-client coverage, build safety, launcher/CLI/TUI/web smoke and Storybook checks passed. Code review completed without findings. Both source archives match all 1,420 tracked files and modes at 215b8b99feacffdbd2eb8709e85f27e95b801534. The extracted eight-file kit passed match/change/invalid/help checks with source reads, network access and writes denied on macOS; its input and kit bytes remained unchanged. SHA256SUMS covers all three archives.

Full validation, smoke, Storybook and coverage on the released main commit also passed.

ToolScope v0.3.0: offline baseline comparison

Compare exported tool definitions directly from a command line:

node scripts/compare-tool-baselines.mjs baseline.json current.json

The command reuses ToolScope’s validated baseline parser. It emits deterministic JSON and exits 0 when definitions match, 1 when they differ and 2 for invalid input. It ignores capture times and object-key order, reports tool additions/removals and changed top-level fields, and preserves both input files. Regular UTF-8 files, strict schema checks and bounded reads prevent invalid or excessive inputs from becoming successful reports. Runnable synthetic examples are included.

Root runtime dependencies update to Undici 8.11.2, fast-uri 3.1.8 and ip-address 10.7.2. The current production dependency audits report zero matches across the five installs. Weekly reviewed Dependabot updates coordinate shared dependencies across those installs; automatic merging is disabled.

Verification: full validation and coverage on the exact released commit passed, including all four clients, built launcher/CLI/terminal/browser smoke flows and Storybook interactions. Independent GPT-6 Astra review closed the shared-parser coverage finding. A fresh root-only install from the source archive passed all six actual offline-command cases and both documented examples. Both attached archives match all 1,416 tracked files and executable modes at 928915cd64bf6520c90f30b04aca40e0e49fd65f; SHA256SUMS records their hashes.

Use: download and extract either source archive. Node 24 is required. For the offline comparison alone, install the root production dependencies without install hooks:

npm ci --omit=dev --ignore-scripts
node scripts/compare-tool-baselines.mjs examples/tool-baselines/before.json examples/tool-baselines/after.json

The synthetic example intentionally exits 1: it reports the added inspect_part tool and changed lookup.description. The README covers full browser, CLI and terminal setup.

The comparison reports definition changes, not backward compatibility or authenticated server history. No external provider or production deployment was exercised. ToolScope adapts MCP Inspector with retained attribution, licenses and notices. This GitHub source release is version 0.3.0; inherited package metadata remains 2.8.0. It is not an npm publication.

ToolScope v0.2.0: portable baselines

ToolScope v0.2.0 completes the saved-baseline workflow with Import baseline.

Export definitions in one session, clear the browser baseline, and restore the file for the same catalog server identity. Imports preserve the original capture time. Replacing an existing baseline requires explicit confirmation; invalid files, cancellation, and storage errors preserve the saved reference.

The parser rejects mismatched server/tool identities, malformed definitions, duplicate JSON properties, excessive nesting, and numeric overflow. Equivalent JSON key order no longer creates false changes. File size is checked before reading, and existing incomplete-tool-list restrictions still apply to comparisons.

Verified locally: 27 affected tests, per-file coverage above the existing 90% gates, lint/format/typecheck/web build. In Chrome, a real bundled-server baseline was exported, cleared, imported, reloaded and compared successfully. Adding a synthetic tool, refreshing, and comparing reported exactly one addition. No external provider or production server was used.

The application still requires its local backend and is intended for desktop viewports of at least 1280 pixels. Comparisons identify changed definition fields; they do not prove compatibility. Imported files are not authenticated historical evidence. ToolScope adapts MCP Inspector; upstream source, licenses and notices remain. This source-release version is independent of the inherited package version.

Full CI 36335788802 passed on 3f3c916: validation, all four clients' per-file coverage, build safety/externalization gates, launcher/CLI/TUI/web smoke checks, Chromium flows and Storybook interactions. Final commit 943a0bd records that result without code changes.

The regenerated source archive matches all 1,409 files and executable modes at the final commit. SHA-256: d770bc0ea1740822f633fc089c1d2c7a863e3d47747385956c57ce2a718328f5.

ToolScope v0.1.0

ToolScope provides local MCP inspection in a browser, command line, and terminal interface. It includes runnable local servers and saved tool-schema baselines.

• Save advertised tool definitions, refresh or reconnect, and compare additions, removals, and changed fields.
• Block comparisons against stale, incomplete, malformed, or excluded tool lists.
• Export baseline JSON and retain it across browser reloads.
• Keep default example catalogs and runtime state within the project; explicit server sources retain precedence.

Use Node.js 24 and the README setup. The web interface requires its local authenticated Node backend; this is a source release, not a hosted service or npm package.

The desktop interface requires at least 1280 pixels of width. Comparison reports definition changes, not compatibility guarantees. Baseline import and mobile support are not part of this release.

ToolScope adapts MCP Inspector 2.8.0. Applicable code, documentation, and dependency notices are retained in LICENSE and NOTICE.

Verified release commit: 67986a7ce8976dfaeb2b44427bd2a30bf2729c8f. The Linux CI run passed formatting, lint, types, builds, unit/integration coverage, build safety checks, launcher/CLI/terminal/browser smoke tests, and Storybook interactions. All four clients passed the 90% per-file coverage gates. Local setup and the saved-schema workflow were also exercised on macOS.