bouncer-mcp
The local stdio MCP proxy half of bouncer.
It sits between your MCP client and your existing tool servers, re-exports every
tool 1:1, and enforces bouncer-core's
contracts on each call.
uv tool install bouncer-mcp
bouncer init --config path/to/mcp-config.json
The enforcement engine — provenance and taint rules, per-argument constraints,
call budgets — is bouncer-core, which depends only on pyyaml and speaks no
MCP at all. Install that one directly if you are enforcing contracts inside your
own harness rather than proxying an MCP server.
There is no LLM in the enforcement path. Every decision is plain Python over a recorded schema, a policy, and a taint log.
Full documentation, the threat model, and the benchmark results are in the repository README.
1 maintainer
Metadata
1 maintainer
Release files for bouncer-mcp 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| bouncer_mcp-0.1.3.tar.gz | 19.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bouncer_mcp-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.6 kB
Release files / bouncer_mcp-0.1.3.tar.gz
| Download URL | bouncer_mcp-0.1.3.tar.gz |
|---|---|
| Size | 19.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
366c95f678595ba78e97f43eaa9ece4056fccbee72f11734a9b96d7bac9665cb
|
|
BLAKE2b-256 checksum How to use checksums |
c6b1a984d254e076b00d0494b7e0dcf549f5b183627baa99da22f00de89b6008
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 23, 2026.
Transparency logRelease files / bouncer_mcp-0.1.3-py3-none-any.whl
| Download URL | bouncer_mcp-0.1.3-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c6c29c39da81a711ffcb1c4c33fc14e870789239fe1a7d4f6d0112045ccff8c
|
|
BLAKE2b-256 checksum How to use checksums |
994c0e773e500d21b25bc67b52c611d475e4d63e09d587682887b3c9875d9ce0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 23, 2026.
Transparency logSecurity for bouncer-mcp 0.1.3
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for bouncer_mcp-0.1.3.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 Oct 23, 2026.
Transparency logA 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.
