World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
Local MCP server for policy-authorized semantic context and source-authority reconciliation.
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 | 12/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 | 12/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.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 16, 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 Semantic State Runtime 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": { "semantic-state-runtime": { "command": "npx", "args": [ "-y", "semantic-state-runtime" ] } } } 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 Semantic State Runtime 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": {
"semantic-state-runtime": {
"command": "npx",
"args": [
"-y",
"semantic-state-runtime"
]
}
}
}Use Semantic State Runtime and tell me what you can do for me, then show me one thing✓ If Claude says it is using Semantic State Runtime or shows a Semantic State Runtime 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 Semantic State Runtime yet
Semantic State Runtime runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Semantic State Runtime
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 Semantic State Runtime 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 semantic-state-runtime -- npx -y semantic-state-runtime 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 Semantic State Runtime 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 semantic-state-runtime -- npx -y semantic-state-runtimeYou should see Semantic State Runtime listed as connected
Use Semantic State Runtime and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Semantic State Runtime or shows a Semantic State Runtime 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 Semantic State Runtime 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": { "semantic-state-runtime": { "command": "npx", "args": [ "-y", "semantic-state-runtime" ] } } } 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 Semantic State Runtime 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": {
"semantic-state-runtime": {
"command": "npx",
"args": [
"-y",
"semantic-state-runtime"
]
}
}
}Use Semantic State Runtime and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Semantic State Runtime or shows a Semantic State Runtime 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 Semantic State Runtime 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": { "semantic-state-runtime": { "type": "stdio", "command": "npx", "args": [ "-y", "semantic-state-runtime" ] } } } 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 Semantic State Runtime 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": {
"semantic-state-runtime": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"semantic-state-runtime"
]
}
}
}Use Semantic State Runtime and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Semantic State Runtime or shows a Semantic State Runtime 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
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user semantic-state-runtime -- npx -y semantic-state-runtimeClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"semantic-state-runtime": {
"command": "npx",
"args": [
"-y",
"semantic-state-runtime"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"semantic-state-runtime": {
"command": "npx",
"args": [
"-y",
"semantic-state-runtime"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"semantic-state-runtime": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"semantic-state-runtime"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: semantic-state-runtimeBased 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 16, 2026
The registry name was verified with the GitHub account oaslananka, which owns the repo
Code last changed yesterday
Uses MIT
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 semantic-state-runtime@0.3.3
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/oaslananka-semantic-state-runtime)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 yesterday, and the latest version (0.3.3) reached the registry today.
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. 97 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 Semantic State Runtime | 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 | MIT | 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.
Semantic State Runtime
Switch AI coding agents without losing the current project facts.
Connect one public GitHub repository or selected local folder, then ask your MCP-capable AI agent for the open issues and relevant decisions. SSRL keeps a bounded, read-only project view updated on demand and applies explicit source authority instead of trusting stale local notes.
Status: public npm MCP release (current version in the npm badge). The MCP runtime is usable
with synthetic data, but independent human onboarding and production use are
not yet validated. No hosted service or model account is included.
Semantic State Runtime (SSRL) helps AI agents use the right information when several sources disagree. It reconciles writable state against explicit source authority, persists the result across sessions and exposes only policy-authorized context through the Model Context Protocol (MCP).
Imagine a project deadline is November 15 in a stale local copy, but the trusted source says November 20. Rather than letting an AI assistant guess, SSRL can:
This is state reconciliation and access-controlled context, not simply chat-history memory, an unrestricted file search, or an LLM provider.
npm install -g semantic-state-runtime
ssrl-connect https://github.com/oaslananka/semantic-state-runtime cd ssrl-semantic-state-runtime opencode
Ask: "Use SSRL context.compile for oaslananka/semantic-state-runtime. Which GitHub issues are currently open? Show issue numbers and sources." The generated OpenCode configuration is ready; Antigravity's workspace-local .agents/mcp_config.json and a separate Copilot MCP entry are included.
Alternatively, connect a local folder once using ssrl-connect ./my-project --out ./my-project-ssrl. It discovers the project's GitHub origin when present, or accepts --local-only. Existing files are never modified; only selected Markdown, and GitHub open issue/PR metadata when connected, are ingested. The bounded refresh runs when context is requested, not through a background service. This is not an automatic history of every chat or file.
See the one-command project connection guide for exact limits, private GitHub access, refresh timing, source authority and reproducible acceptance evidence.
Requirements: Node.js 24.12+ and npm. No Git clone, workspace build, API key, or model account is needed to try the synthetic read-only MCP server.
npm install -g semantic-state-runtime
ssrl-demo-init ./ssrl-example ssrl-node --version
The initializer creates a new folder and refuses to overwrite one. It writes read-only synthetic Markdown and ready-to-use client definitions:
./ssrl-example as the working directory; the generated opencode.json uses the installed server's absolute paths.ssrl entry from ./ssrl-example/copilot.mcp-config.json into your existing global mcp-config.json (merge; do not replace other configured servers).The underlying ssrl.config.json limits access to synthetic records and does not grant writes. Ask the client to call context.compile for Project Atlas deadline; the authorized response contains 2026-11-20. A model account may be needed by your chat client, not by SSRL itself. Client definitions are generated inside the demo folder; your global configuration is never modified.
Use the explicit configuration guide before authorizing access to real files. Windows and Linux registry installs plus MCP tool calls passed with synthetic data; independent human onboarding and production suitability remain unverified.
See installation and client setup.
Requirements: Node.js 24.12+ and pnpm 12.14.0. From a fresh clone:
pnpm install --frozen-lockfile
pnpm build pnpm demo:handoff
The demo uses synthetic Markdown/SQLite data and two actual MCP SDK client sessions. Its output shows the stale value, trusted value, state.plan/state.apply reconciliation, restarted runtime, authorized context.compile answer, and privacy checks. Package installation may use the network; the demo itself requires no API key or external model.
Walk through the real observed output.
For a source-built alternative, see the source-based Developer Preview installer. It builds a production-only installation at an explicit final path; the source-based Windows installation cannot safely be moved afterward. The published npm package is standalone, separate from that limitation.
Maintainers can still build a private local npm tarball using pnpm preview:pack -- and verify it with pnpm test:preview-pack. The stable npm package is publicly available with GitHub release provenance. The Registry listing must be verified separately against the official MCP Registry API; independent consumer acceptance has not yet been established.
When running a local source build instead, after creating an explicit configuration file using the local runtime guide, start the server with:
node packages/node-app/dist/cli.js ./ssrl.config.json
./ssrl.config.json is your own file, not an included ready-made production config. Use explicit source mappings, principal scopes, field policies and local paths. The server does not silently discover user files. Point your MCP-capable client's stdio command and arguments at the built CLI and that config; each chat client has a different config format.
| MCP tool | What it does |
|---|---|
state.plan | Computes a bounded proposed change based on source authority and preconditions. |
state.apply | Applies an approved proposal only within configured write permissions. |
context.compile | Returns current, policy-scoped semantic context within a bounded token budget. |
Start read-only. Grant only state:read and context:read when a client needs retrieval, and disable writable field policies and plan/apply. The first-run OpenCode setup creates such a temporary synthetic read-only workspace automatically:
pnpm demo:chat-setup
The setup is offline; an actual hosted-model chat request requires a separate, explicit developer API key and network access.
OpenCode v2.3.0 and Goose CLI v1.59.0 each made a real context.compile MCP call and returned the correct authorized deadline from synthetic data. They are two independently tested chat applications, not two independently hosted model providers: both used the same NVIDIA developer gateway on one Windows host. These tests do not establish physical cross-device synchronization or readiness for real user data.
See OpenCode and Goose examples and the separate live two-model handoff.
latest), read-only synthetic first-run, local build, deterministic demo, stdio MCP integration and regression tests.source systems / local files
↓ connectors + restart-safe ingestion ↓ immutable Artifact Plane + Semantic State Store ↓ bitemporal state / retractions / typed identity / relations ↓ incremental Context Capsules ↓ Context Access Gateway ↓ retrieval / future agent adapters
AI side effects: agent -> RuntimeHost plan/apply -> provider preconditions -> journal
Implemented checkpoints include:
context.compile projection with authenticated context:read preflight;Core constraints are intentionally stricter than a conventional "RAG over personal files" system:
See docs/invariants.md and the versioned design documents under docs/.