World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Diagnose a repo for AI agents: context noise, missing commands, cache value, flaky tests.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 27/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 | 39/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 177 (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 dev-diagnosis. Follow https://mcp.popnx.com/i/wjddidi-1-dev-diagnosis.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 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 dev-diagnosis 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": { "dev-diagnosis": { "command": "npx", "args": [ "-y", "dev-diagnosis-cli" ] } } } 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 dev-diagnosis 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": {
"dev-diagnosis": {
"command": "npx",
"args": [
"-y",
"dev-diagnosis-cli"
]
}
}
}Use dev-diagnosis and tell me what you can do for me, then show me one thing✓ If Claude says it is using dev-diagnosis or shows a dev-diagnosis 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 dev-diagnosis yet
dev-diagnosis runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect dev-diagnosis
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 dev-diagnosis 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 dev-diagnosis -- npx -y dev-diagnosis-cli 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 dev-diagnosis 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 dev-diagnosis -- npx -y dev-diagnosis-cliYou should see dev-diagnosis listed as connected
Use dev-diagnosis and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using dev-diagnosis or shows a dev-diagnosis 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 dev-diagnosis 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": { "dev-diagnosis": { "command": "npx", "args": [ "-y", "dev-diagnosis-cli" ] } } } 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 dev-diagnosis 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 dev-diagnosis and tell me what you can do for me, then show me one thing✓ If Cursor says it is using dev-diagnosis or shows a dev-diagnosis 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 dev-diagnosis 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": { "dev-diagnosis": { "type": "stdio", "command": "npx", "args": [ "-y", "dev-diagnosis-cli" ] } } } 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 dev-diagnosis 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 dev-diagnosis and tell me what you can do for me, then show me one thing✓ If VS Code says it is using dev-diagnosis or shows a dev-diagnosis 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 dev-diagnosis -- npx -y dev-diagnosis-cliClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"dev-diagnosis": {
"command": "npx",
"args": [
"-y",
"dev-diagnosis-cli"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"dev-diagnosis": {
"command": "npx",
"args": [
"-y",
"dev-diagnosis-cli"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"dev-diagnosis": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"dev-diagnosis-cli"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: dev-diagnosis-cliBased 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 WJDdidi-1, which owns the repo
Code last changed today
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
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/wjddidi-1-dev-diagnosis)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 today, and the latest version (0.2.4) reached the registry 3 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 dev-diagnosis | 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.
One diagnosis for your repo, your commands, your cache and your tests.
npx dev-diagnosis-cli all
One command. No install, no config. It tells you what your AI coding agent shouldn't be reading — and what that's costing you in tokens.
React ships 46 yarn.lock files, one per fixture directory — 6.4 MB your agent reads before it sees a line of source. We measured it:
$ npx dev-diagnosis-cli all # in a React checkout
Score: 96/100 — ~2,141,395 tokens wasted every turn
$ npx dev-diagnosis-cli all --fix # writes 3 lines to .aiignore Score: 100/100 — 0 tokens wasted
Same story everywhere we looked: Node.js wastes ~24.8M tokens a turn on vendored deps, Next.js ~7.4M, Deno ~6.9M — mostly test fixtures and build output nobody reviews. (Full measurements of 10 famous repos.)
all also checks why a command isn't found (path), whether your build cache actually pays (cache), which tests are flaky (flakes), and the largest native binaries (binaries) — and it serves everything as an MCP server (--mcp) so your agent can call it directly. --only runs only the named checks and --skip runs all but the named ones (comma-separated: context, binaries, path, flakes, cache — the two cannot be combined): the cache check runs the build twice, so all --skip cache is the fast path when the build itself is not under suspicion, and skipped checks are listed as skipped so the summary stays honest.
$ dev-diagnosis all
Files: 9 Size: 1.68 MB Score: 75/100 — Some context noise found Noise to keep away from an AI agent: data/export.json — large file (1.68 MB, ≈ 439k tokens) Estimated tokens wasted on this noise: ≈ 439k tokens (estimate, ~4 bytes per token) FAIL some context noise found (score 75/100)
$ dev-diagnosis context --fix Created .aiignore with 1 entry: data/export.json Re-scanned after fix: Score: 94/100 — Looks clean for an AI coding agent PASS context is clean
$ dev-diagnosis all Files: 9 Size: 1.16 KB Score: 94/100 — Looks clean for an AI coding agent PASS context is clean
The noise cost 439k tokens a turn; the fix is one entry in .aiignore.
dev-diagnosis alldev-diagnosis binariesdev-diagnosis flakes ci-runs/dev-diagnosis cache -- npm run buildcommand not found in the IDE but works in the terminal: dev-diagnosis path | Check | Needs | Finds | Cannot find |
|---|---|---|---|
context | a directory | files your agent should not read, and what they cost in tokens | whether a large file is actually needed — it flags by size, you decide |
binaries | a directory | the largest native binaries and their hardening (PIE, NX, RELRO, stripped, entropy) | whether any of it is exploitable — it is a checkup, not an audit |
path | a command name | which shell contexts resolve it, shadowed copies, toolchain installs | why a command that resolves still crashes when it runs |
cache | a build command and a cache directory | whether the cache pays, cold vs warm | whether a different cache setup would be faster |
flakes | JUnit XML from two or more runs | flaky, always-failing and passed-on-retry tests, ranked | why a test is flaky — only that it is |
npx dev-diagnosis-cli
Or install it once and use it anywhere:
npm install -g dev-diagnosis-cli
dev-diagnosis all
Rather not install it by hand? Paste this to your coding agent: "Install dev-diagnosis (npm install -g dev-diagnosis-cli if it's not on PATH), then run dev-diagnosis setup so you can use it."
dev-diagnosis with no arguments is the same as dev-diagnosis all on the current directory, and dev-diagnosis is the same as dev-diagnosis all . Each check is also available on its own:
dev-diagnosis context [path] # files an AI agent should not read
dev-diagnosis path # why a CLI command is missing dev-diagnosis cache -- # cold vs warm timing for a build cache dev-diagnosis flakes # flaky tests from JUnit XML across runs dev-diagnosis all [path] --command --flakes --
all always runs context on [path] (default: the current directory) and runs path, flakes and cache when their input is given. Checks without their input are listed as skipped, with the command that would run them, instead of silently pretending they ran. A build command on a repo with no cache directory to measure is also listed as skipped rather than failing: nothing to measure is not a problem. --json gives machine-readable output for context, path, cache, flakes and all. In all --json, a check that could not run (a missing runs directory, a failing build) reports { "error": " " } instead of null, so a script can tell why the overall result failed. Add --fix to context (or all) to write the suggestions into /.aiignore instead of only printing them: entries already there are left alone, nothing else in the file is touched, and a later scan skips everything .aiignore lists — so context --fix followed by context comes back clean. Add --dry-run with --fix to preview first: it lists the entries that would be added, diff-style, and writes nothing — and exits 1 when the fix would change .aiignore, even when the score passes (like prettier --check), 0 only when nothing would change and the repo passes.
all ends with a one-line summary: how many checks passed, failed or were skipped, how much context noise was found, and what the cache saved when it ran. In --json output the same fields are in the summary object. Add --report to all to also write the run as a Markdown report — the same score, noise list with token costs, suggestions and verdicts, in prose you can paste to an agent or attach to a PR, instead of copying terminal output by hand. It works with --json (the JSON on stdout stays parseable) and with --fix (the report reflects the post-fix re-scan).
Exit codes: 0 every check that ran passed; 1 a check found something to fix or could not run; 2 usage error. With --fix, the exit code follows a re-scan after the fix, so a fix that leaves the repo clean exits 0 — the command reports the repo as it stands after the fix, not as it was before. With --fix --dry-run nothing is written, so the exit code is 1 when the fix would change .aiignore — even when the score passes — and 0 only when the fix would change nothing and every check passes.
Shell completion for bash, zsh and fish: dev-diagnosis completion bash prints a completion script generated from the same command list the CLI parses, so it can never suggest a flag the CLI rejects. Install it with, e.g. dev-diagnosis completion bash > ~/.bash_completion.d/dev-diagnosis, or source <(dev-diagnosis completion bash) for a one-off session. Mistyped a flag anyway? The CLI suggests the closest match (Did you mean ...?) instead of a bare error.
dev-diagnosis setup detects the agents on your machine (Claude Code, Codex CLI, Cursor, Gemini CLI, VS Code) and writes the MCP config that wires dev-diagnosis into each of them. It prints a preview of exactly what will be written before writing anything: a config that already mentions dev-diagnosis is left alone, a config that exists without it is merged (other entries kept), a missing config is created. A config it cannot parse is left alone and reported.
dev-diagnosis setup # preview, then write
dev-diagnosis setup --dry-run # preview only, write nothing dev-diagnosis setup --check # report which agents are wired (exit 0 when all are) dev-diagnosis setup --hooks # install native git hooks instead (see Pre-commit hook)
setup --hooks installs the commit-time enforcement as native git hooks — no pre-commit, no husky: it writes .githooks/pre-commit and .githooks/commit-msg (the same two commands the Husky section documents) and sets core.hooksPath to .githooks. Commit .githooks/ and every clone gets the hooks. It never overwrites a hook file or a hooks path it did not install, and setup --hooks --check reports whether they are installed.
If dev-diagnosis itself is not on PATH, setup says so — install it globally (npm install -g dev-diagnosis-cli) or the agents will not be able to run it.
dev-diagnosis doctor checks the installation itself: Node version, dev-diagnosis and git on PATH, the home directory setup and --skill-generate write into, installed skills (and whether their frontmatter is valid — a broken one silently never triggers), MCP wiring and .aiignore. It is read-only — it changes nothing, so it works even when the rest of the tool is misbehaving — and every failure comes with a copy-paste fix. Warnings are for optional wiring (a missing skill, an unwired agent); only failures make it exit 1. --json gives the same checklist as data. The method is Claude Code's claude doctor: one command that answers "is my install healthy?" instead of debugging each piece by hand.
dev-diagnosis --mcp serves the checks as MCP tools over stdio — no extra install, no network, the same code the CLI runs. Add it to your agent once:
Claude Desktop: the repo ships a manifest.json (MCPB, the renamed DXT format) — pack it with npx @anthropic-ai/mcpb pack and drag the .mcpb file onto Settings → Extensions. The bundle is just the server (zero dependencies, so there are no node_modules to bundle), and .mcpbignore keeps tests, docs and tooling out of it.
Claude Code (.mcp.json in the repo, or claude mcp add dev-diagnosis -- dev-diagnosis --mcp):
{
"mcpServers": { "dev-diagnosis": { "command": "dev-diagnosis", "args": ["--mcp"] } } }
Codex (codex mcp add dev-diagnosis -- dev-diagnosis --mcp, or in ~/.codex/config.toml):
[mcp_servers.dev-diagnosis]
command = "dev-diagnosis" args = ["--mcp"]
Gemini CLI (in ~/.gemini/settings.json, under mcpServers — the same shape as Claude Code's):
{
"mcpServers": { "dev-diagnosis": { "command": "dev-diagnosis", "args": ["--mcp"] } } }
To keep the agent inside one repo, add --sandbox (alias --root): paths outside it are rejected with a plain error. Add --read-only to serve only the read-only tools: diagnose_cache is not listed at all (it runs a build command), and diagnose_context, diagnose_all and diagnose_secrets lose their write inputs (fix, buildCommand, writeSecretsBaseline) and declare readOnlyHint: true — so a host that auto-approves read-only tools can call them without prompting, and a call that asks for a write anyway gets a tool error instead of a write. The method is GitHub's official MCP server's --read-only mode. Seven tools: `di