neko-harness-doctor vs HarnessScope
neko-harness-doctor is a plugin bundle for AI coding tools published by aliksir. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). HarnessScope is an MCP server published by moongioh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.2.3 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.3 Downloads/month (npm): 112 Downloads/week (npm): 13 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | neko-harness-doctor | HarnessScope |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (hscope) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/aliksir/neko-harness-doctor | github.com/moongioh/harness-scope |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
neko-harness-doctor
Diagnose your Claude Code harness (CLAUDE.md, settings.json, .mcp.json, hooks, skills, memory, MCP servers, and workflow) against 25 anti-pattern indicators. Outputs an S–E overall grade, per-category scores, violations with evidence citations, and prioritized Quick Wins. Includes an interactive fix flow: `--fix-mode propose` emits structured JSON proposals that Claude Code applies via the Edit tool with per-item user approval. Deterministic (no LLM — grep/AST/JSON only), zero runtime dependencies, bilingual (Japanese default, English via `--lang en`). When installed as a plugin, the bundled skill auto-triggers on natural-language requests like "diagnose my harness" and exposes `/neko-harness-doctor` as a slash command.
HarnessScope
Turn-level governance observability for Claude Code transcripts. Local-first, no LLM inside.
How to run each
neko-harness-doctor As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install neko-harness-doctor@claude-community
HarnessScope As a local MCP server: npm package
claude mcp add --transport stdio hscope -- npx -y hscope mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of neko-harness-doctor publish no settings it asks for, so we do not compare settings.
What it can do: neko-harness-doctor · What it can do: HarnessScope · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.