About this integration
MCP policy proxy: enforces a code of conduct across connectors before the upstream is called.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.8.3
- Package
- aggrete
- Last compatibility test
- Not independently tested
Connect your agent
aggretePinned publisher README and manifest reviewed offline; package and integration endpoint were not executed or independently security-audited.
Capabilities: Proxy MCP connector calls through code-of-conduct policy checks, Apply cross-call memory, redaction, and per-user access controls
Connected profiles
Additional details
io.github.Aggrete/aggrete
Source ↗ · Checked 2026-09-170.8.3
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17aggrete
Source ↗ · Checked 2026-09-180.9.0
Source ↗ · Checked 2026-09-18Publisher documents a stdio identity mode for its proxy; runtime and upstream connectors were not tested.
Source ↗ · Checked 2026-09-18Authentication varies by deployment and upstream connector, including held credentials, per-user delegation, and OAuth.
Source ↗ · Checked 2026-09-18Run aggrete with a proxy configuration and connect the MCP client to the proxy process.
Source ↗ · Checked 2026-09-18Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-18