Documentation
A server can change what its tools do after you approved it, and your agent will call the new one without noticing. mcpgawk reads every MCP server your agents can reach, checks every call against a baseline you approved, and blocks the ones that changed. On your machine, uploading nothing.
Quickstart
Install, first run, and turning protection on. Every step says what you should see, and what to do when you do not see it.
CLI reference
All 18 commands, every flag, printed from the shipped parser.
Clients
The 21 agent configs it reads, where it reads them, and the 6 that can block a call.
Troubleshooting
Every state it can report, every exit code, and the failures real testers hit.
Install
uv tool install --force mcpgawk && mcpgawk
No account, no key, nothing to sign up for. The first run reads your agent configs, lists what
it finds, and offers to turn protection on. No uv?
curl -LsSf https://astral.sh/uv/install.sh | sh — no admin rights needed.
What it does not do
- It cannot check an agent it has no hook point in. 15 of
the 21 clients have none. They are named in
mcpgawk statusrather than quietly left out. - It cannot scan an account-hosted connector. Those run in a vendor's cloud and expose no local endpoint. They are listed as exactly that.
- It never reports a run it could not finish as clean. That case exits 4 and says incomplete.
- It does not record tool arguments. The call log is metadata, so it cannot become the richest secret on your disk.