aka-kika/mcpock

-6b8e6b)
A small Mac menu bar app that checks every MCP server your AI agents use, and
tells you which ones are broken, slow, waiting for a sign-in, or set up
differently from one agent to the next.
MCP (Model Context Protocol) servers are the small programs that give agents
like Claude Code, Cursor or Codex their extra tools. mcpock finds them in your
agents' config files, starts each one the way the agent would, and checks that
it answers.
## Why
When you use more than one agent, the same MCP server ends up in five config
files, each written a little differently. One day a tool quietly stops working
in one agent and not the others, and you only notice when a task fails halfway.
The agent rarely says why.
mcpock gives you one place to look. It never changes your configs: it reads
them, checks every server, and shows you what needs attention and why, so you
(or your agent) can fix it.
## What's new in 1.13
Next step: every reason has a line under it saying what to do, on the card,
in status.md and in mcpockproblems.
A fix turns green by itself: save a changed config and mcpock checks that
server again within seconds, with no click. Nothing is written.
Smaller: the footer says two numbers, three ways to copy instead of six, a
shorter Settings > General, and Usage counts as one switch, off for new installs.
Full notes: 1.13.0. Earlier: 1.12.2, 1.12.1, 1.12.0.
## What it does
Finds your servers automatically. It knows the config files of the common
agents and also scans the usual config folders for anything written in a
standard MCP format. The same server in several agents shows as one row.
Checks each one. It starts a local server (or calls a remote one), does
the MCP handshake, asks for its tool list, then closes it. Every 15 minutes
by default (1 minute to 4 hours, or only when you click Refresh). It also
watches the config files it knows, without writing to them: a saved change is
read within seconds and only the servers it touched are checked (not in Manual).
A config file in a new place is found at launch or when you click Refresh. A server that is already fine
keeps its tool list between rounds; Refresh and Check again ask for it anew.
Shows health as a shape, not only a colour:
| Shape | Means |
| Filled dot (green) | Fine: it started and listed its tools |
| Ring (amber) | Slow (no answer in 20 s, tried twice; 10 s for a remote server) or needs sign-in (HTTP 401/403) |
| Ring (grey) | Still checking |
| Diamond (red) | Broken: could not start, quit on start, or refused the handshake |
| Dash (grey) | Paused by you, or runs inside its own app and can't be checked from outside, or Needs Wake open: it belongs to a Mac app that is closed (not broken; it is checked again as soon as the app opens) |
Spots servers set up differently. When one agent launches a different
command or address than the others (often an old path), the row says so, and
Compare shows each agent's version side by side. The same runtime in
another folder (npx here, an agent's own ~/.agent/node/bin/npx there) is not a
difference. If the agents are
meant to differ, choose Mark as intended on the card (or Mark as
Intended in the right-click menu).