mcpgawk MCP server

One gateway in the path. On your machine.

mcpgawk

<!-- mcp-name: io.github.gawk-dev/mcpgawk -->

Your agents call Model Context Protocol servers that can change what their tools do after you approved them, and the agent will call the new one without noticing. mcpgawk reads every server your agents can reach, checks every call against a baseline you approved, and blocks the ones that changed. It runs on your machine and uploads nothing.

The same engine powers mcpgawk Platform: mcpgawk enforce puts one endpoint in front of the whole fleet with a key per caller, policy on every call and a hash-chained audit log, and mcpgawk monitor watches the servers you approved around the clock and tells you when one drifts. This free layer is the seeing and the blocking underneath it. mcpgawk Platform is one subscription per person for up to 3 machines: start a free 7-day trial at https://mcp.gawk.dev/trial.html (no card) or subscribe at https://mcp.gawk.dev/subscribe. Then mcpgawk login on this same install fetches the paid engine and turns those on — one more command, nothing else to set up.

Watch: mcpgawk in 64 seconds. A tool you approved changes in an update; mcpgawk refuses the call until you decide.

mcpgawk demo — its own output, in a sandbox that touches nothing of yours. Run the same command and you get the same thing.

Why

A server you approved can change what its tools do afterwards. Nothing in MCP tells your agent that happened — it just calls the new tool. That is the rug-pull, and it is the case mcpgawk is built for.

Two things follow from being able to see a server properly. You find out what each one can reach before you trust it, and you find out what it costs: every tool is loaded into your context on every request, used or not.

How it's different

Shortened. The full README is on GitHub.