Back to search
mcp-canary
MCP serverGitHub
Zero-config health checks and schema-drift alerts for the MCP servers you have installed
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/dasandner--mcp-canary)HTML
<a href="/listings/dasandner--mcp-canary"><img src="/api/listings/dasandner--mcp-canary/badge.svg" alt="findsafeskills safety rating" /></a>Install
i
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
cargo install --git https://github.com/DaSandner/mcp-canary
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 76 lines
- # mcp-canary
- **Find out when the MCP servers you use break or change — before your agent quietly works around them.**
- MCP servers fail silently. A tool disappears after `npx -y …@latest` pulls a new version, a parameter changes type, a server hangs on the handshake. Nothing errors; your agent just starts using a nearby tool or answering from memory.
- `mcp-canary` reads the MCP configs you already have, connects to every server, and remembers each tool's schema. Run it again later and it tells you exactly what changed.
- ```
- $ mcp-canary diff
- Running fresh check...
- ! Project .mcp.json/hang connect: initialize failed: no response to `initialize` within 30s
- 2 change(s):
- - legacy in Project .mcp.json/fake
- ~ search in Project .mcp.json/fake (schema changed)
- + param limit
- ~ param q: "string" -> "number"
- ! limit is now required
- ```
- ## Install
- ```sh
- cargo install --git https://github.com/DaSandner/mcp-canary
- ```
- ## Usage
- ```sh
- mcp-canary scan # list every MCP server found in your configs
- mcp-canary check # connect to each one, list tools, save a snapshot
- mcp-canary diff # re-check and compare against the last snapshot
- ```
- | Flag | Effect |
- | --- | --- |
- | `--timeout <secs>` | Max wait per server response (default 30) |
- | `check -v` | Print every tool name |
- **Exit codes:** `0` all good · `1` a server failed or a schema changed · `2` mcp-canary itself errored. That makes it usable in a cron job, a git hook, or CI.
- ## Where it looks
- | Client | Config |
- | --- | --- |
- | Claude Desktop | `~/Library/Application Support/Claude/claude_desktop_config.json` |
- | Claude Code | `~/.claude.json` (global and per-project servers) |
- | Cursor | `~/.cursor/mcp.json`, `./.cursor/mcp.json` |
- | VS Code | `./.vscode/mcp.json` |
- | Any project | `./.mcp.json` |
- Snapshots live in `~/.mcp-canary/` (`latest.json` plus a `history/` folder).
- ## What it checks
- - The `initialize` handshake completes within the timeout
- - `tools/list` returns (with pagination)
- - Tools added or removed since the last snapshot
- - Input-schema changes, with parameter-level detail: added/removed params, type changes, newly required params
- A server that fails during `diff` is reported as unreachable, not as "all tools removed", and its last good snapshot is kept.
- ## What it doesn't do (yet)
- - **Remote (HTTP/SSE) servers** are listed but skipped
- - **No tool calls.** It checks the contract, not whether results are correct. It never executes a tool, so it is safe to run against servers with write access.
- - Windows and Linux config paths for Claude Desktop are not read yet
- ## Related
- If you **build** MCP servers and want to test one in depth (replayed calls, fuzzing, contract files), look at [EnjoyableWork/mcp-doctor](https://github.com/EnjoyableWork/mcp-doctor). `mcp-canary` is for people who **use** a pile of servers and want one command that says "something you rely on changed."
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.