World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
A bounded local evidence tool with current agent permission checks and durable retry handling.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 7/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Continuity Evidence. Follow https://mcp.popnx.com/i/zerohourzulu-continuity-evidence.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Continuity Evidence for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "continuity-evidence": { "command": "npx", "args": [ "-y", "@ramex-labs/continuity-mcp", "--config" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Continuity Evidence tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"continuity-evidence": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp",
"--config"
]
}
}
}Use Continuity Evidence and tell me what you can do for me, then show me one thing✓ If Claude says it is using Continuity Evidence or shows a Continuity Evidence tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Continuity Evidence yet
Continuity Evidence runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Continuity Evidence
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Continuity Evidence for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user continuity-evidence -- npx -y @ramex-labs/continuity-mcp --config 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Continuity Evidence tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user continuity-evidence -- npx -y @ramex-labs/continuity-mcp --configYou should see Continuity Evidence listed as connected
Use Continuity Evidence and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Continuity Evidence or shows a Continuity Evidence tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Continuity Evidence for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "continuity-evidence": { "command": "npx", "args": [ "-y", "@ramex-labs/continuity-mcp", "--config" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Continuity Evidence tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
~/.cursor/mcp.json
Paste these settings, fill in the empty values and save
{
"mcpServers": {
"continuity-evidence": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp",
"--config"
]
}
}
}Use Continuity Evidence and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Continuity Evidence or shows a Continuity Evidence tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Continuity Evidence for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "continuity-evidence": { "type": "stdio", "command": "npx", "args": [ "-y", "@ramex-labs/continuity-mcp", "--config" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Continuity Evidence tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
MCP: Open User Configuration
Paste these settings, fill in the empty values and save
{
"servers": {
"continuity-evidence": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp",
"--config"
]
}
}
}Use Continuity Evidence and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Continuity Evidence or shows a Continuity Evidence tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user continuity-evidence -- npx -y @ramex-labs/continuity-mcp --configClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"continuity-evidence": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp",
"--config"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"continuity-evidence": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp",
"--config"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"continuity-evidence": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ramex-labs/continuity-mcp",
"--config"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 18, 2026
The registry name was verified with the GitHub account zerohourzulu, which owns the repo
Code last changed 37 days ago
Uses Apache-2.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for @ramex-labs/continuity-mcp@0.3.0-preview.12
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/zerohourzulu-continuity-evidence)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 37 days ago, and the latest version (0.3.0-preview.12) reached the registry 38 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Continuity Evidence | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Message package preview — 10 October 2026: Core11, remote6, gateway11 and evidence12 add the optional saved-record explanation command. See the current release guide. Existing API/policy/proof behavior stays unchanged; older npm archives remain available.
Source preview.13: MCP client/server/core updated to 2.2.0 for GHSA-6qxp-vccf-f47h. New MCP archives are source-prepared; npm and Registry still select the earlier published tuple.
Previous source preview.12.1: Plain-language messages, completed historical ZK experiments, and retained-receipt reader source. The installable packages now include the optional saved-output explanation command; use the exact tuple in the release guide.
Current developer preview: Exact versions and installation.
Follow an investigation: Follow one protected case through interruption, replacement, a signed completion, new evidence and a persistent challenge. Run the walkthrough.
Continue an existing case: Same case, longer history, preserved permissions and unfinished duties. Start with supported profiles, migration and recovery, or the protected evidence example.
Core 0.3 preview: Build a fresh case, connect approved MCP tools, or run the public tests. The original 0.2.2 evaluation releases remain available.
[Explore the interactive demo →](https://zerohourzulu.github.io/continuity/) · Start here · Developer guide · Security and limits
[Try your own choices in the playground →](https://continuity.ramex.com/playground/) No installation or account needed.
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 original tutorial 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.
| You want to… | Start here | What you will learn |
|---|---|---|
| Understand the idea without installing anything | The story and answer key | Why an unfinished duty and permission are separate. |
| Run and inspect a replacement | Tutorial, then operator commands | What was refused, who holds the duty and what B may do. |
| Evaluate or integrate the code | Core 0.3 quickstart | Create your own permissions, try a protected tool, then connect a framework or policy engine. |
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:
git clone https://github.com/zerohourzulu/continuity.git
cd continuity
<!-- /quickstart -->
See the result first, without installing dependencies:
node examples/recorded.mjs
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:
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:
node tutorial/start.mjs --deny-review
B still inherits the duty, but its review permission becomes DENY. Expected output and explanation · Setup checks and recovery.
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.
| Your next step | Where to go |
|---|---|
| See the idea and recorded comparison | Interactive demo |
| Inspect your new run and optional recorded Linux evidence | Operator guide |
| Integrate an authority check | Developer guide · Executable reader example |
| Try optional native enforcement mechanics | Disposable Linux lab |
| Review source provenance and validation | Validation · Presentation checks · Provenance |
| Extend the presentation | Website maintenance |
Presentation maintainers can find the separate owner-private edition in website maintenance. The public walkthrough needs no account.
Read the short development history from Core 0.1 to the current reference implementation. Contributions and public RFCs are welcome; an RFC is useful for changes to protocol behavior or security boundaries.
Core 0.2.2 is local reference software. It is not a hostile-agent sandbox, production credential system or autonomous cyber defender. The website selects recorded results; the downloaded tutorial executes Core. Real integrations must mediate every consequential operation through a protected executor. Security boundaries.
The source, tutorial, tests, reader and website are included here and in the complete evaluation download. Earlier editions remain available as historical releases; use evaluation.6 for the commands above. Package overview · Presentation provenance.
Release status and licensing · Apache 2.0 license · Third-party notices
Try the standalone developer package: install the supplied JavaScript SDK tarball in a separate application, create one authorized synthetic packet, and inspect why refused requests create none. Includes TypeScript declarations and an offline consumer check. This is an evaluation interface around unchanged Core0.2.2.
The shared-package preview connects the cooperating remote tools and MCP evidence tool to one Core dependency. Try native LangChain tools and lost-reply recovery, or the MCP evidence tool.