Skip to main content

mcpgawk by nativerse

One gateway in the path. On your machine.

mcpgawk on Product Hunt
Featured on Product Hunt.

mcpgawk

PyPI Python License CI Open VSX GitHub Marketplace Local-first

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: your servers, approvals and call log stay there, and nothing about them is sent unless you ask for it (mcpgawk push, --supply-chain).

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?utm_source=github&utm_medium=readme (no card) or subscribe at https://mcp.gawk.dev/subscribe. Then mcpgawk login <key> on this same install fetches the paid engine and turns those on — one more command, nothing else to set up.

mcpgawk in 64 seconds: a tool you approved changes in an update, and mcpgawk refuses the call until you decide. Watch the video.

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

mcpgawk demo: a server is approved, changes afterwards, and the guard blocks the tool that appeared

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

  • It blocks, it does not only report. A scanner tells you afterwards. mcpgawk guard installs one pre-execution hook and a tool that appeared after you approved the server does not run.
  • It runs the server, not just reads it. mcpgawk verify drives tools in a sandbox and reports what they actually did — exfiltration, SSRF, poisoning — reproduced before it is reported.
  • Your inventory stays on your machine. Cloud scanners send your inventory to a server and gate the verdict there. Every decision here is made on your machine, and the free tools need no account.
  • It says what it did not check. Skipped tools are named as skipped, never counted as clean.

Features

  • 🛑 Block a changed tool before it runs — running mcpgawk puts one pre-execution hook in the loop of each agent on your machine that has a hook point (mcpgawk guard install does Claude Code alone). The decision is local, in about 10ms, with nothing to sign in to. Works on 6 of the 21 supported clients; the rest have no hook point and are named, not glossed over.
  • 🧪 Run it, don't just read it — mcpgawk verify drives tools in a sandbox and reports what they did: exfiltration, SSRF, tool poisoning, secret leaks. The sandbox is a proxy by default, so it needs no Docker; Docker adds full container isolation when you have it. Safe mode drives only provably read-only tools, and every tool it skips is named as skipped.
  • 🧑‍⚖️ Approval needs a person — mcpgawk decide opens a local screen for what changed. The buttons live on the tokened link printed in your terminal, and mcpgawk refuses an approval when it can see an agent running it.
  • 🖥️ One local panel — mcpgawk panel: every server, every decision, every piece of evidence.
  • 📜 The changelog no vendor publishes — mcpgawk changes shows every change to a server's tool surface between the snapshots you have recorded: tools added or removed, input schemas widened, descriptions and annotations rewritten. It reads your local history, so it works for a server you approved weeks ago — the one thing a fresh scan can never tell you.
  • 🔌 Any transport — stdio, streamable-HTTP, SSE, and OAuth remotes (via the mcp-remote bridge).
  • 💸 Token cost index — exactly what each tool adds to your context at connect, plus the 3 heaviest tools.
  • 🧾 Capability facts — write / exfil-capable / declared annotations, straight from the schema, plus a trust-surface summary (% write, % exfil-capable, destructive-declared count) and an annotation-completeness score.
  • 📌 Integrity pin + drift — catch a server that silently rewrites its tools. Every scan is recorded locally; --no-track skips it.
  • 🚩 Bounded signals — injection-shaped descriptions, cross-server shadowing, under-declaring Server Cards — pointers for a human, never verdicts.
  • 🔒 Your inventory stays on your machine — the measurement layers import no network library. Enforced by a test. Two checks are opt-in and make an explicit exception (see Guarantees): --supply-chain and --oauth-scopes.

Get it — three ways

Install mcpgawk from PyPI, the VS Code Marketplace or Open VSX (13-second film)

CLI (any terminal):

uv tool install --force mcpgawk      # or: pipx install --force mcpgawk
mcpgawk                              # finds every agent config on the machine itself

Run it as an MCP server: mcpgawk mcp (stdio), or uvx mcpgawk mcp.

Editor (VS Code / Cursor): install mcpgawk from the VS Code Marketplace or Open VSX. It is a sidebar panel: every MCP server configured across your AI tools, grouped by the tool it lives in, with what each one can reach and which need attention. The extension drives this engine as a subprocess — it is built and released separately, so its source is not in this repository.

CI (GitHub Action): gate every PR on token budget, flagged signals and, with a committed baseline, a server that changed since you approved it (Marketplace):

- uses: gawk-dev/mcpgawk@v1
  with: { config: mcp.json, max-tokens: 8000, fail-on-flagged: true }

When to run it

  • Once, then leave it on — mcpgawk guard install. After that a tool that appears on a server you already approved does not get called.
  • Before you add a server — see what it costs and what it can do, before you trust it.
  • When your agent feels slow or picks the wrong tool — it's often MCP bloat (too many / too-heavy tools).
  • On every PR — the CI gate catches creeping token cost and flagged signals, and, given a committed baseline, a server that changed since you approved it.
  • If you publish an MCP server — see what it costs your users and how it reads to a client, and fix it (usually one line per tool). Lean + well-annotated is a differentiator.

Use

mcpgawk                                  # first run: every agent config on this machine
mcpgawk demo                             # the whole arc in a sandbox — approve, drift, block
mcpgawk guard install                    # put the baseline in your agent's loop
mcpgawk guard status                     # is protection actually on?
mcpgawk decide                           # what changed, and approve it as a human
mcpgawk panel                            # the local page: servers, decisions, evidence
mcpgawk verify mcp.json                  # run the servers and watch what they do
mcpgawk changes                          # what changed on your servers since you approved them
mcpgawk login <key>                      # licence? one command fetches the paid engine (enforce, monitor)

Scanning on its own, if that is all you want:

mcpgawk scan mcp.json                                              # a whole config
mcpgawk scan --stdio "npx -y @modelcontextprotocol/server-filesystem@2026.8.31 /tmp"
mcpgawk scan --http https://host/mcp --header "Authorization: Bearer $TOKEN"
mcpgawk scan --sse  https://host/sse
mcpgawk scan mcp.json                                             # recorded locally: the next scan reports what changed
mcpgawk scan mcp.json --no-track                                  # measure without recording
mcpgawk scan mcp.json --json                                      # machine-readable labels
mcpgawk scan mcp.json --verbose                                   # full per-tool table, not just flagged tools
mcpgawk scan mcp.json --supply-chain                              # opt-in: npm/PyPI deprecation check (network)
mcpgawk scan mcp.json --oauth-scopes                              # opt-in: decode a supplied Bearer JWT's scope

Keep tokens out of the config file. Under mcpgawk wrap, an env value written as keychain:<service> (or keychain:<service>@<account>) is read from your macOS Keychain when the server starts and placed in the server's environment only. The config holds a reference, the agent sees a reference, mcpgawk stores nothing. A reference that cannot be read refuses to start the server and names the reference, never a value.

"github": { "command": "mcpgawk", "args": ["wrap", "--", "npx", "-y", "@modelcontextprotocol/server-github"],
            "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "keychain:gh-work" } }

What it reports

  • Cost index — tokens each tool adds at connect (named tokenizer; a comparable index, not an absolute Claude count), plus the 3 heaviest tools.
  • Trust surface — capability facts (write/mutating, exfil-capable, declared annotations) rolled up into % write, % exfil-capable, and a destructive-declared count.
  • Annotation completeness — a transparent composite (annotated ÷ total tools declaring read/write intent), not a risk score.
  • Coverage — tools, prompts, and resources counted (--verbose for the full per-tool table).
  • Integrity pin — a hash that changes if the server silently rewrites its tools. Scans are recorded locally by default, which turns it into rug-pull detection over time (--no-track skips it).
  • Bounded signals — precise, low-false-positive pointers for a human to review, never verdicts: injection-shaped descriptions (tools and prompts), cross-server name shadowing, and public Server Cards that under-declare what the server actually exposes.
  • Supply-chain (opt-in, --supply-chain) — checks the launched package against the public npm/PyPI registry for deprecation/yank status.
  • OAuth scopes (opt-in, --oauth-scopes) — locally decodes a supplied Bearer JWT's scope claim.

Guarantees

  • Your servers, approvals and call log stay on your machine. Nothing about them is sent unless you ask for it (mcpgawk push, --supply-chain). Every network connection mcpgawk makes:

    • the protocol client talking to the servers you point it at;
    • one anonymous request to PyPI about once a day asking whether a newer mcpgawk exists (it says nothing about your servers; MCPGAWK_NO_UPDATE_CHECK=1 turns it off);
    • --supply-chain, only when you pass it: sends the launched package's name (and pinned version, if any) — never your tool inventory — to the public npm registry or PyPI JSON API;
    • mcpgawk install-node, only when you run it: downloads Node from nodejs.org;
    • mcpgawk login, only when you run it: sends your key to mcp.gawk.dev, and a paid key is checked with Lemon Squeezy;
    • mcpgawk push, only when you run it: sends a scan report to your hosted fleet view.

    The measurement layers import no network library — they cannot egress by construction (enforced by a test). Public Server Card discovery is fetched with no auth and no redirect-following. --oauth-scopes makes no network call at all; it locally decodes a Bearer JWT you already supplied.

  • Facts ≠ heuristics. Exact capability facts and the token index never mix with the bounded heuristic signals — separate in code, separate in output.

  • Reproducible. One command, identical numbers.

  • Tracks the protocol. Built on the official mcp SDK, which negotiates the protocol version.

Develop

uv run --extra dev --with mcp --with tiktoken --with httpx python -m pytest -q

CI gate — GitHub Action

Scan your MCP servers on every pull request and fail the build if one gets too heavy or trips a signal. Give it a committed copy of your approvals and it also fails when a server changed since that copy, or is not in it. It runs entirely in your runner — your inventory stays there — and posts a per-server cost/flag table to the job summary.

- uses: gawk-dev/mcpgawk@v1
  with:
    config: mcp.json        # local (stdio) servers named in it are started on the runner
                            # or: stdio / http / sse — a single server
    baseline: mcpgawk-baseline.json   # optional: a committed copy of your ~/.mcpgawk/history.json
    max-tokens: 8000        # fail if any server loads more than this at connect
    fail-on-flagged: true   # fail if any bounded signal fires

Without baseline there is nothing to compare against, so changes are not checked. The baseline file is only read. It records your server names and who approved them, so commit it only where that is fine to share.

Available on the GitHub Marketplace.

Contributing

Issues and PRs welcome. Please read CONTRIBUTING.md first, and see the design boundaries in THREAT-MODEL.md. Security reports go through SECURITY.md (privately, not a public issue).

License

Apache-2.0 — see LICENSE. Part of the nativerse · gawk.dev family. Site and docs: mcp.gawk.dev. The value is in the repo, not a cloud.

Use it from your agent (skill)

Let your coding agent run the checks itself — whenever it adds, upgrades or audits an MCP server:

# Claude Code: install the plugin (the skill, nothing else)
/plugin install mcpgawk --marketplace gawk-dev/mcpgawk

# Any other agent: copy the skill folder into its skills directory
mkdir -p ~/.claude/skills && cp -r plugin/skills/mcpgawk ~/.claude/skills/mcpgawk

The skill teaches the agent to measure a server BEFORE trusting it and relay every consent prompt to you verbatim.

Metadata

Release files for mcpgawk 0.1.90

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcpgawk 0.1.90
File Size Uploaded Provenance Actions
mcpgawk-0.1.90.tar.gz 7.6 MB With provenance Details for mcpgawk-0.1.90.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mcpgawk 0.1.90
File Interpreter ABI Platform Actions
mcpgawk-0.1.90-py3-none-any.whl Python 3 none any Details for mcpgawk-0.1.90-py3-none-any.whl

Total release size: 12.7 MB

Release files / mcpgawk-0.1.90.tar.gz

Download URL mcpgawk-0.1.90.tar.gz
Size 7.6 MB
Tags Source
SHA-256 checksum
How to use checksums
fd9ae4a5bd7a5f584088471a6bde1e4546579e7697945864735633a56e8ee6a8
BLAKE2b-256 checksum
How to use checksums
31cfb3169e7bab4a11b895ff6e274cba56b26b92d21a97b6e93e4a5a4cd119d6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.

Transparency log

Release files / mcpgawk-0.1.90-py3-none-any.whl

Download URL mcpgawk-0.1.90-py3-none-any.whl
Size 5.2 MB
Tags Python 3
SHA-256 checksum
How to use checksums
7b98526ddf2a6cb4e39a96c3c6f4853efc6f3f2eb0f2c963319422e51f6cb07a
BLAKE2b-256 checksum
How to use checksums
d65c49b1ade706c8f26e7e9e39e6e0353a7cd77333135d0fe425dab7a0bd538f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.

Transparency log

Security for mcpgawk 0.1.90

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for mcpgawk-0.1.90.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.90 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page