Continuity Evidence runs on your own machine — the client starts it, so there is no endpoint to ping. 62 installs a week from npm. Last commit 12 Oct 2026.
A bounded local evidence tool with current agent permission checks and durable retry handling.
What the code does
We read the source, 3 d ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
"runuser",
const result=spawnSync(process.execPath,[join(root,'tools/sdk-build/node_modules/typescript/bin/tsc'),'-p',join(root,'tools/sdk-build/tsconfig-core-0.3.json'),'--outDir',join(scratch,'dist')],{stdio:'inherit'});
e('genesis','DEPLOYMENT_INITIALIZED',0,{domain:config.domain,adapterPolicyHash:core.PORTABLE_ADAPTER_POLICY_HASH,canonicalLineageId:`lineage:${caseId}`,versions:{eventSchemaVersion:`continuity-event/${VERSION}`,receiptSchemaVersion:`continuity-receipt/${VERSION}`,queryEnvelop…
const c=this.child=spawn(this.config.command,this.config.args,{cwd:this.config.cwd,env:getDefaultEnvironment(),shell:false,stdio:['pipe','pipe','ignore']});
self.process = subprocess.Popen(command, cwd=ROOT, stdin=subprocess.PIPE,
fs.mkdirSync(path.join(base,name), {mode}); fs.chmodSync(path.join(base,name),mode);
for(const name of ['continuity','continuity-remote'])delete lock.packages['node_modules/@ramex-labs/'+name];
"path": ".npmrc",
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check Continuity Evidence every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add continuity-evidence -- npx -y @ramex-labs/continuity-mcp{
"mcpServers": {
"continuity-evidence": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp"
]
}
}
}[mcp_servers.continuity-evidence]
command = "npx"
args = ["-y", "@ramex-labs/continuity-mcp"]{
"mcpServers": {
"continuity-evidence": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp"
]
}
}
}{
"servers": {
"continuity-evidence": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp"
]
}
}
}Alternatives to Continuity Evidence
same job, measured the same wayLocal MCP gateway for approved jobs, current agent permissions and durable retry inspection.
AI testing harness with Jay: risk-based checks, bug investigation, and local evidence reports.
Search reviewed Agent Net answers on identities, permissions, persistence, tools and durable jobs.
Action-required AI dependency changes and tested tools with reproducible evidence.
Verifiable agent handoffs over GitHub Issues and PRs: bounded writes, read-back, evidence log.
Local decisions, evidence, outcomes and reviewed lessons with bounded retrieval and an HTML viewer.
Temporary encrypted Rust Playgrounds shared by agents and people, with permissioned local Run/Debug.
Local working notes, decisions, evidence and resumable sessions with SQLite persistence.
Continuity Evidence — questions
Answers built from our own checks of this server.