dev-diagnosis

● Active

io.github.WJDdidi-1/dev-diagnosis

Diagnose a repo for AI agents: context noise, missing commands, cache value, flaky tests.

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "dev-diagnosis": {
      "command": "npx",
      "args": [
        "-y",
        "dev-diagnosis-cli@0.2.2"
      ]
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add dev-diagnosis -- npx -y dev-diagnosis-cli@0.2.2
OpenAI Codex CLI
codex mcp add dev-diagnosis -- npx -y dev-diagnosis-cli@0.2.2
VS Code
code --add-mcp '{"name":"dev-diagnosis","type":"stdio","command":"npx","args":["-y","dev-diagnosis-cli@0.2.2"]}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Testing & QA
Version
0.2.2
Registry
active
Published
11/13/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 17, 2026

Looks healthy: dev-diagnosis is maintained, open source.

Maintained
Active
Last commit 7 days ago (Nov 15, 2026), 0 open issues.
Official registry
Active
Published as io.github.WJDdidi-1/dev-diagnosis in the official MCP registry, version 0.2.2.
Source
Open source, Apache-2.0
Public repository under the Apache-2.0 licence, 0 stars, 0 forks.
Runs
On your machine
A local npm package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 15, 2026
Stars
0
Forks
0
Last push
Nov 15, 2026
License
Apache-2.0

JavaScriptai-agentai-codingbuild-cacheclaude-codeclicontext-windowdeveloper-toolsdevtoolsdiagnosticsflaky-testsgithub-actionmcpmodel-context-protocolnodejs

From the README

dev-diagnosis One diagnosis for your repo, your commands, your cache and your tests. 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. It pays for itself in three lines 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: 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), and which tests are flaky (flakes) — 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, 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. Try it: three steps, one fix The noise cost 439k tokens a turn; the fix is one entry in .aiignore. When you reach for it • Just took over a repo: dev-diagnosis all • A repo vendors native binaries, or you are about to ship one: dev-diagnosis binaries • CI goes red, then green on retry, then red again: dev-diagnosis flakes ci-runs/…

Read the full README on GitHub →

The most-starred Testing & QA servers in the index, with their live-check result.

ServerStarsLast pushLive check
Keploy19,937Nov 2026Needs sign-in
e2e14,110Nov 2026Local / not checked
Mockserver5,011Nov 2026Local / not checked
Reticle1,326Nov 2026Local / not checked
Flutter Skill409Sep 2026Local / not checked

dev-diagnosis: questions people ask

Is dev-diagnosis a remote or a local MCP server?
According to its entry in the official MCP registry, dev-diagnosis ships as a local package (npm) that your client starts on your machine.
Is dev-diagnosis safe to use?
Looks healthy: dev-diagnosis is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, Apache-2.0; runs: On your machine; credentials: None declared. Serverdex check of Nov 17, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is dev-diagnosis still maintained?
Active: the repository's last commit 7 days ago. Last push Nov 15, 2026, 0 GitHub stars, Apache-2.0 licence. Read from GitHub on Nov 15, 2026.
How do I add dev-diagnosis to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. ci-triageGroup failed GitHub Actions runs by root cause; separate real regressions from flaky failures.
Browse all Testing & QA →

Add the badge to your site

Show visitors that dev-diagnosis is listed here — it’s also the link we check for a free listing.

dev-diagnosis — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-wjddidi-1-dev-diagnosis?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="dev-diagnosis — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![dev-diagnosis — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-wjddidi-1-dev-diagnosis?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-wjddidi-1-dev-diagnosis) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-wjddidi-1-dev-diagnosis) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-wjddidi-1-dev-diagnosis)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-wjddidi-1-dev-diagnosis"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-wjddidi-1-dev-diagnosis"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-wjddidi-1-dev-diagnosis"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).