Case file No.308 · pypi · stdio

mcpgawk

io.github.gawk-dev/mcpgawk · v0.1.79

Measure MCP servers, pin the approved tool surface, refuse calls to tools that changed. Local-first.

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 1 days ago

Source transparency15/15

public repo, license Apache-2.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

415 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v0.1.79)Oct 21, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is mcpgawk safe?

MCPWatch gives mcpgawk a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does mcpgawk have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package mcpgawk. That is not proof of safety.

When was mcpgawk last updated?

The latest registry version is 0.1.79, published Oct 20, 2026. The last push to gawk-dev/mcpgawk was on Oct 20, 2026. MCPWatch last checked it on Oct 21, 2026.

What license does mcpgawk use?

GitHub reports the license of gawk-dev/mcpgawk as Apache-2.0.

Related servers

same publisher / similar score