BackBond Agent Scan MCP server

BackBond Agent Scan

BackBond Agent Scan is published as the exact scoped package @backbond/agent-scan@0.6.3. Static only: it inspects tool metadata and agent configuration already on your machine. It does not run tools, probe a live agent, upload traces, contact a hosted service, or execute a second binary.

If a result from this scanner or from a BackBond publication looks wrong, open a correction through the false-positive form. We respond within 72 hours.

Try the browser preview

Watch the 50-second synthetic walkthrough, then try the synthetic example. The silent video has on-screen text and a transcript. It shows a verified scanner 0.6.3 result for supplied metadata, not runtime behavior.

Try Agent Scan in your browser: three synthetic MCP examples, followed by a local check of your own tools/list JSON. No account or installation is required. The page processes the manifest in memory without uploading it.

The browser preview uses Agent Scan 0.6.3 and checks supplied MCP tool metadata only, up to 200 tools and 256 KiB. It does not assess runtime behavior, and a non-blocking result is not a safety determination or insurance decision. Use the pinned CLI below for other supported formats, larger inputs, or offline workflows.

Static MCP tool manifest inspection

BackBond Agent Scan helps operators vet MCP tools before attachment through local, deterministic static MCP tool manifest inspection. It reports findings and missing evidence without executing proposed tools. Results do not establish runtime safety.

Vet MCP tools before attachment

Export the proposed server's real tools/list response, then inspect that supplied manifest with the pinned vet-tools instructions below. A block result stops automatic attachment; review requires operator review; noblockingfinding means no configured blocking rule fired on the supplied metadata. The scanner itself does not enforce attachment or create insurance coverage.

Install from a trusted host first

For operator-enforced checks on an existing stdio MCP connection, see the separate Agent Scan stdio gate. It starts the authorized server and gates tool attachment and calls; it is not included in the scanner npm package, does not sandbox startup, and does not verify runtime behavior. The checksum-verified standalone scanner and pinned npm paths below remain available for manual checks.

For a hardened or network-isolated agent, an operator should download the single-file release asset and checksum on a network-enabled trusted host, verify it, and transfer the verified file through the organization's approved software path:

curl -fLO https://github.com/BackBond/agent-scan/releases/download/v0.6.3/agent-scan.cjs
curl -fLO https://github.com/BackBond/agent-scan/releases/download/v0.6.3/agent-scan.cjs.sha256
sha256sum --check agent-scan.cjs.sha256
node agent-scan.cjs scan

Before attaching a proposed MCP or supported function-tool list, first save the real exported manifest as tools-list.json in the current directory. vet-tools reads that file; it does not create it:

node agent-scan.cjs vet-tools --stdin < tools-list.json

agent-scan.cjs is an unminified, auditable, dependency-free build of the same tagged CLI. It runs scan, vet-tools, and the mcp stdio entrypoint without npm installation or network access.

Verify the published bytes

The protected release workflow publishes package-registry provenance and attaches the registry-authoritative tarball, its SHA-256, the deterministic standalone file, and its SHA-256 to the matching source tag. A reviewer can rebuild both artifacts from public source:

Shortened. The full README is on GitHub.