trending

When you approve an MCP server, what happens at its next version?

We launched here last Monday. One number from our prep keeps coming up in conversations, so a question.

We ran every stable version of 14 of the top 30 npm MCP servers from March to September in a throwaway environment, tools/list only. 86 version-to-version transitions. 40 of them changed what the tools do or accept, 47%. The largest category was not added tools. It was rewritten parameter descriptions, 92 of them. The agent reads that text and acts on it. The person approved the server once and never reads it again.

mcpgawk sits on that gap: baseline at approval, refuse the call when the surface changes until a human looks. https://mcp.gawk.dev/ph if you want to try it.

So: when you add an MCP server to Claude Code, Cursor or Codex, what do you do at its next version? Pin it, re-read the tools, or trust the update?

mcpgawk - Catch MCP servers that change after you approved them

An MCP server can change what its tools do after you approved it. Your agent will call the new one and never notice. mcpgawk records a baseline of every MCP server your agents use, checks behaviour in a sandbox, and sits in the path: once a tool's description or power changes, the call is refused until you decide. The agent cannot approve its own way past it. Everything runs on your machine. Nothing is uploaded. Free CLI, VS Code extension and MCP server. The gateway tier has a 7-day trial.