mcp-medic 1.0.2 → 1.0.3

package/README.md

@@ -8,6 +8,9 @@ Diagnose broken MCP (Model Context Protocol) server configs before they break yo
 
 `mcp-medic` validates MCP server configurations, executes full protocol initialization handshakes across stdio/SSE/HTTP transports, checks all exposed tool JSON schemas against standard specifications, and simulates sample calls — providing actionable suggestions and CI-ready exit codes.
 
+> [!NOTE]
+> **Naming & Installation**: The npm package for this tool is **`mcp-medic`** (`npx mcp-medic` / `npm i -g mcp-medic`). While this GitHub repository is named `mcp-doctor`, an unrelated older package already occupies the npm name `mcp-doctor` (different author). Users who want this tool must install **`mcp-medic`**, not `mcp-doctor`.
+
 ## Why this exists
 
 A broken MCP server config usually doesn't fail loudly — it fails as your agent silently missing a tool, retrying a handshake forever, or getting a malformed schema it can't reason about. Those bugs are miserable to track down after the fact. `mcp-medic` catches them at the config level, before an agent ever touches the server: it actually connects (real `initialize` handshake, real `tools/list`), so "the config parses" and "the server actually works" are checked together, in CI, with a real exit code.
@@ -43,6 +46,8 @@ This is the whole point (a real handshake, not a schema guess) — but it means
 
 ## Quick Start
 
+> **Preferred invocation**: Run `npx mcp-medic` (the npm package is `mcp-medic`, not `mcp-doctor`).
+
 ```bash
 # Run against auto-discovered configs in current project / Claude Desktop
 npx mcp-medic
@@ -195,6 +200,7 @@ The `security.*` checks are heuristic — they pattern-match on what a server *d
 - **`security.*` checks are heuristic pattern-matching**, not a security audit — see the note above. They can both miss real issues and flag benign configs (e.g. a legitimate local dev server on plain `http://`).
 - **Fleet commands (`check-all`, `diff`) are newer and less battle-tested** than `check`/`watch` — the core check pipeline they're built on is the same, but edge cases in glob matching or drift diffing are more likely.
 - **The VS Code extension and community check packages are not shipped/published** — see the sections above.
+- **npm README sync**: Latest docs live on GitHub main; npm README updates on the next publish.
 - **First run via `npx`** pays a one-time cost to resolve and download the package; once installed (or on a warm npx cache), `--help`/`--version` return in well under 100ms.
 
 ---
@@ -205,6 +211,11 @@ The `security.*` checks are heuristic — they pattern-match on what a server *d
 - 📋 See [CONTRIBUTING.md](./CONTRIBUTING.md) before opening a PR
 - 📝 [CHANGELOG](./CHANGELOG.md)
 
+> [!NOTE]
+> **Repository Metadata (GitHub Settings)**: The GitHub repository About description and topics must be configured directly in repository settings (cannot be set from repository files):
+> - **Description**: `Diagnose broken MCP server configs before they break your agent. npm: mcp-medic`
+> - **Topics**: `mcp`, `model-context-protocol`, `cli`, `diagnostics`, `linter`, `claude`, `vscode`, `security`, `ci`
+
 ## Governance, Stability & Security
 
 - 🏛️ [Governance & Project Sustainability](./GOVERNANCE.md)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-medic",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Diagnose broken MCP (Model Context Protocol) server configs before they break your agent silently.",
   "type": "module",
   "main": "dist/index.js",