Continuity Evidence MCP server

Core 0.3 preview: Build a fresh case, try the protected MCP tool, or run the public tests. The original 0.2.2 evaluation releases remain available.

Continuity — agents change; responsibility remains

Explore the interactive demo → · Start here · Developer guide · Security and limits

Developer preview · Apache 2.0. Release status.

A process supervisor can start Agent B. Continuity records which role B occupies, which powers it has, what happened before, and which unfinished duties survive the change. A replacement receives its explicitly granted powers; an unfinished duty does not silently grant more authority.

The demonstration follows a security investigation interrupted by an agent replacement. The old request is refused, the investigation stays OPEN, and the successor’s review permission is checked independently.

Choose your path

Run the tutorial

Use Node 22.18+ (22.x), 24.x or 26.x on macOS or Linux. Prefer the latest patch of your chosen release. No global pnpm or Python is needed for this tutorial. Full quickstart, including archive extraction.

Get the public source; no GitHub account is needed:

<!-- quickstart:clone -->

git clone https://github.com/zerohourzulu/continuity.git
cd continuity

<!-- /quickstart -->

See the result first, without installing dependencies:

<!-- quickstart:recorded -->

node examples/recorded.mjs

<!-- /quickstart -->

Expect ALLOW for reviewing the investigation and DENY for collecting another packet. This inspects a bundled recorded case; it does not execute a new action.

Generate your own evidence:

<!-- quickstart:run -->

node tools/setup.mjs
node tutorial/start.mjs

<!-- /quickstart -->

Expect PASS — duty remains OPEN; B has no collection power, then VERIFIED. Setup downloads locked dependencies with scripts disabled. The tutorial then runs locally using synthetic data and public test keys. It prints your new case name and exact follow-up commands. Rerunning creates another case and preserves earlier evidence.

Change one permission:

<!-- quickstart:compare -->

node tutorial/start.mjs --deny-review

<!-- /quickstart -->

B still inherits the duty, but its review permission becomes DENY. Expected output and explanation · Setup checks and recovery.

Choose your holder of record.

Keep records locally, or choose a chain-backed deployment to make selected history publicly verifiable. Cryptographic commitments can let authorized reviewers check private records without publishing their contents. This tutorial runs locally; each deployment has its own privacy, availability and finality requirements.

Explore and build

Shortened. The full README is on GitHub.