World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Deterministic, resumable multi-agent workflows across Codex, Claude, Cursor, and Kimi.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 9/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 | 17/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 Wiff. Follow https://mcp.popnx.com/i/xxxoooxoxo-wiff.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 Wiff 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": { "wiff": { "command": "npx", "args": [ "-y", "@xxxoooxoxo/wiff" ] } } } 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 Wiff 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": {
"wiff": {
"command": "npx",
"args": [
"-y",
"@xxxoooxoxo/wiff"
]
}
}
}Use Wiff and tell me what you can do for me, then show me one thing✓ If Claude says it is using Wiff or shows a Wiff 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 Wiff yet
Wiff runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Wiff
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 Wiff 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 wiff -- npx -y @xxxoooxoxo/wiff 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 Wiff 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 wiff -- npx -y @xxxoooxoxo/wiffYou should see Wiff listed as connected
Use Wiff and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Wiff or shows a Wiff 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)
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 Wiff 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": { "wiff": { "command": "npx", "args": [ "-y", "@xxxoooxoxo/wiff" ] } } } 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 Wiff 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
Use Wiff and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Wiff or shows a Wiff 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)
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 Wiff 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": { "wiff": { "type": "stdio", "command": "npx", "args": [ "-y", "@xxxoooxoxo/wiff" ] } } } 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 Wiff 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
Use Wiff and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Wiff or shows a Wiff 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 wiff -- npx -y @xxxoooxoxo/wiffClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"wiff": {
"command": "npx",
"args": [
"-y",
"@xxxoooxoxo/wiff"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"wiff": {
"command": "npx",
"args": [
"-y",
"@xxxoooxoxo/wiff"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"wiff": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@xxxoooxoxo/wiff"
]
}
}
}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 19, 2026
The registry name was verified with the GitHub account xxxoooxoxo, which owns the repo
Code last changed 2 months ago
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 @xxxoooxoxo/wiff@0.9.1
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/xxxoooxoxo-wiff)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 2 months ago, and the latest version (0.9.1) reached the registry 2 months 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 Wiff | 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.
Harness-agnostic, deterministic, resumable multi-agent workflows — written as plain JavaScript. Like `wf`, but wiff.
Fan a task out to a fleet of agents with a small script instead of a prayer. You write ordinary JavaScript with agent(), /goal stages, parallel(), and pipeline(); the runtime executes it in the background, journals every step, and — when a run dies halfway through — resumes it without re-paying for a single completed agent. A disposable MCP bridge talks to a persistent local daemon, so active workflows outlive the Codex, Claude Code, Cursor, or cron process that launched them while each child runs on Codex, Claude, Cursor, or Kimi.
export const meta = {
name: "audit", description: "Audit files in parallel, fix confirmed issues in isolation", phases: [{ title: "Audit" }, { title: "Fix" }], };
phase("Audit"); const findings = await parallel( args.files.map((file) => () => agent(Audit ${file} for auth bugs, { key: audit:${file}, // stable key → free replay on resume sandbox: "read-only", schema: findingSchema, // structured JSON output }), ), );
phase("Fix"); return await parallel( findings.filter((f) => f.real).map((f) => () => agent(Fix: ${f.summary}, { key: fix:${f.file}, agentType: "surgeon", // persona from .codex/agents/surgeon.md isolation: "worktree", // own git worktree — parallel writes can't collide sandbox: "workspace-write", }), ), );
When one stage must keep working until a condition is genuinely satisfied, make it a native Codex goal:
phase("Verify and repair");
await agent("/goal Make the unit tests pass and verify the final run.", { key: "tests-green", sandbox: "workspace-write", timeoutMs: 30 * 60 * 1_000, });
Wiff holds the workflow at that statement and continues the same Codex thread while its goal is active. The next stage starts only after the worker marks the goal complete; blocked, paused, or limited goals fail explicitly.
Put durable preferences in ~/.wiff/config.json, with optional project overrides in /.wiff/config.json:
{
"version": 1, "instructions": "Verify before reporting success.", "defaults": { "model": "claude-sonnet-5", "fallbackModels": ["gpt-5.6-sol"] }, "rules": [ { "name": "fix-until-green", "when": { "phase": ["Fix", "Repair"] }, "goal": "Relevant tests must pass.", "options": { "model": "gpt-5.6-sol", "effort": "high" } } ] }
Defaults fill missing agent options; matching rules are explicit user policy and override generated workflow options. Instructions are injected alongside the task, ordered fallback models may cross backends, and applicable preference changes invalidate cached results on resume.
There is no harness-agnostic workflow orchestration system. Every coding harness has some multi-agent story — Claude Code has its Workflow tool, Codex has subagents, Cursor has its own agents — but each one is welded to its harness: its runs live and die with that app, its state is invisible to everything else, and none of them can be driven from anywhere but their own chat window. wiff pulls orchestration out of the harness: a persistent local daemon owns execution and durable on-disk state while each harness gets a disposable stdio MCP bridge. Any MCP client — Codex, Claude Code, Cursor, a cron job — can start, disconnect from, watch, resume, or cancel the same runs, and the orchestration itself is a script rather than a conversation.
Ad-hoc multi-agent orchestration ("spawn some subagents for this") is also great until the run is 40 agents deep and something dies. Workflows-as-code give you:
That screenshot is the feature: the host was killed mid-synthesis, and on resume the four finished agents came back from the journal in 0ms — only the interrupted one re-ran.
parallelSettled() is the explicit opt-out). No silent nulls masquerading as success.isolation: "worktree" gives each writing agent a fresh detached git worktree. Clean ones vanish; dirty ones are kept and listed on the run for you to inspect or merge.agentType: "reviewer" injects a markdown persona as the child's developer instructions, with frontmatter defaults for model/effort/sandbox.Codex (plugin: MCP tools + the $workflow authoring skill):
codex plugin marketplace add https://github.com/xxxoooxoxo/wiff.git
codex plugin add wiff@wiff
Claude Code (plugin: MCP tools + skill):
claude plugin marketplace add xxxoooxoxo/wiff
claude plugin install wiff@wiff
Anything else — the server is on npm (@xxxoooxoxo/wiff) and the official MCP Registry (io.github.xxxoooxoxo/wiff), so registry-aware clients can install it by name, and everything else runs it with npx:
npx -y @xxxoooxoxo/wiff # stdio MCP server
Or from a local checkout:
git clone https://github.com/xxxoooxoxo/wiff.git
codex plugin marketplace add ./wiff codex plugin add wiff@wiff
Then start a new Codex session and either invoke the bundled skill with $workflow or just ask: *"run this as a resumable workflow."*
Installing the plugin auto-approves its five workflow-controller tools so headless and desktop runs don't stop at an MCP approval prompt. Agent filesystem access is still governed per-call by sandbox.
The Codex *plugin* is just packaging. The engine underneath is a plain stdio MCP server, so any MCP-speaking harness can orchestrate wiff workflows. The mental model: both the orchestrator and the workers are pluggable — whoever drives, each agent() child runs on a backend chosen from its model name: gpt-*/o* models run as native Codex threads via a local codex app-server (gpt-6-astra needs Codex CLI >= 0.153.4); current claude-fable-5-1, claude-fable-5, claude-opus-5, claude-sonnet-5, and claude-haiku-4-5 models—or the moving fable/opus/sonnet/haiku aliases—run as headless claude agents, composer-* and grok-* models (including cursor-grok-* slugs) run through the official Cursor SDK (@cursor/sdk) in-process, and kimi-code/* models run as headless kimi processes. A workflow can mix them freely (provider: "codex" | "claude" | "cursor" | "kimi" overrides the inference, WIFF_BACKEND sets the fallback for unrecognized models). On the Claude, Cursor, and Kimi backends, workspace-write requires isolation: "worktree"; Kimi's read-only mode is advisory because print mode auto-approves tools and has no OS sandbox.
Requirements on the machine, regardless of harness: Node >= 22, git if you use isolation: "worktree", and the runtime of whichever backend your agents use — Codex CLI
= 0.144.6
and/or claude CLI installed and authenticated, CURSOR_API_KEY for Cursor agents, or the kimi CLI configured with the requested full model alias (for example kimi-code/k3).
Claude Code — the plugin install above is the easy path. To wire just the server manually:
claude mcp add wiff -- npx -y @xxxoooxoxo/wiff
Tool calls go through Claude Code's own permission system; to skip per-call prompts, allow the five tools in .claude/settings.json:
{ "permissions": { "allow": [
"mcpwiffworkflow_start", "mcpwiffworkflow_status", "mcpwiffworkflow_wait", "mcpwiffworkflow_cancel", "mcpwiffworkflow_models" ] } }
Cursor / Windsurf / Claude Desktop — add the server to the client's mcp.json:
{
"mcpServers": { "wiff": { "command": "npx", "args": ["-y", "@xxxoooxoxo/wiff"] } } }
Notes for non-Codex hosts:
~/.wiff/runs/, so a run started from Codex can be watched, cancelled, or resumed from Claude Code (and vice versa), and the live viewer sees everything.WIFF_DAEMON_IDLE_MS overrides this) and writes its pid, socket, and log to ~/.wiff/daemon.json and ~/.wiff/daemon.log.~/.wiff/control/ drives a challenge-response handshake. The bridge proves daemon identity before transmitting workflow scripts or arguments; the daemon also authenticates every controller request.WIFF_DAEMON_OWNERSHIP_PORT to an available loopback port; Wiff reports the exact conflict rather than treating it as a live owner.PATH, backend credentials, CODEX_HOME, persona paths, and Wiff defaults remain those of the bridge that started the daemon. If they change, gracefully terminate the pid recorded in ~/.wiff/daemon.json (active durable runs resume when the next bridge starts) or wait for the 15-minute idle shutdown.