mcp-outbound-metering
Provider-neutral runtime for recording outbound MCP provider HTTP attempts, buffering usage events in a per-replica SQLite outbox, and exporting signed CloudEvents batches to a trusted ingest boundary.
The provider-facing transport is structural and supports both httpx and
httpx2>=2.9.1,<3. Billing delivery continues to use its own private httpx
client. The package contains no provider credentials, account mappings,
customer identifiers, pricing, or destination configuration.
Production hosts must:
- start one runtime before reporting ready;
- wrap every provider data-plane transport construction site;
- use a writable, non-memory-backed, non-network, per-replica outbox path;
- expose
runtime.health()through readiness; and - allow at least
GRACEFUL_SHUTDOWN_BOUND_SECONDSbefore terminating the process, then add platform stop-grace margin.
The package is alpha software. Public distribution exposes the wire format, not authority: batches require an enrolled key and HMAC signature, while the trusted edge derives the source, account, sink, metric, and policy.
1 maintainer
Metadata
1 maintainer
Release files for mcp-outbound-metering 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_outbound_metering-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for mcp_outbound_metering-0.3.0-py3-none-any.whl |
Release files / mcp_outbound_metering-0.3.0-py3-none-any.whl
| Download URL | mcp_outbound_metering-0.3.0-py3-none-any.whl |
|---|---|
| Size | 93.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e5739e6818b5a59a829cc0df13a669a9b9c3e368b8bc1b07fc412d92b3214fe0
|
|
BLAKE2b-256 checksum How to use checksums |
0621d4ec57d501a4dfda2cfe6e6fb40b10ec688c9194e18a57ee75ff9b8d44ec
|
| 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 Aug 17, 2026.
Transparency logSecurity for mcp-outbound-metering 0.3.0
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 1 file in this release has been uploaded with provenance metadata.
Attestation for mcp_outbound_metering-0.3.0-py3-none-any.whl
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 Aug 17, 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.
