Case file No.414 · pypi · stdio

io.github.Aggrete/aggrete

io.github.Aggrete/aggrete · v0.8.3

MCP policy proxy: enforces a code of conduct across connectors before the upstream is called.

Package ↗GitHub ↗

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 4 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

263 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.8.3)Oct 16, 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 io.github.Aggrete/aggrete safe?

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

Does io.github.Aggrete/aggrete have known CVEs or vulnerabilities?

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

When was io.github.Aggrete/aggrete last updated?

The latest registry version is 0.8.3, published Sep 7, 2026. The last push to Aggrete/aggrete was on Oct 15, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does io.github.Aggrete/aggrete use?

GitHub reports the license of Aggrete/aggrete as Apache-2.0.

Related servers

same publisher / similar score