Apizr MCP plugin
Let an MCP client inspect your Python project and review recorded experiments. Analysis reads your source without running its functions.
Use Apizr 0.4.6 with the matching plugin version. Follow the installation guide, then connect your MCP client.
You choose the project, its access policy and a separate directory for plugins.
The client needs all three paths. Install and enable the plugin before starting
the outerspace-apizr-mcp launcher.
Reading experiment history requires history.read permission. Delivery is
optional and requires its own permissions; enabling analysis does not enable it.
See the MCP guide
for tools, configuration and delivery options.
Python 3.11–3.15 · GPL-3.0-or-later · Release notes
1 maintainer
Metadata
1 maintainer
Release files for outerspace-apizr-mcp 0.4.6
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 | Actions |
|---|---|---|---|---|
| outerspace_apizr_mcp-0.4.6.tar.gz | 26.1 kB | With provenance | Details for outerspace_apizr_mcp-0.4.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| outerspace_apizr_mcp-0.4.6-py3-none-any.whl | Python 3 | none | any | Details for outerspace_apizr_mcp-0.4.6-py3-none-any.whl |
Total release size: 54.2 kB
Release files / outerspace_apizr_mcp-0.4.6.tar.gz
| Download URL | outerspace_apizr_mcp-0.4.6.tar.gz |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ef47e320eda9efd9e1e13d3641fcf9723c860968fd03dd04358a8d406b851f2
|
|
BLAKE2b-256 checksum How to use checksums |
cea94e88fe1aa3248d66e044301d54cefc372d38a7d48f743c78532304034246
|
| 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 19, 2026.
Transparency logRelease files / outerspace_apizr_mcp-0.4.6-py3-none-any.whl
| Download URL | outerspace_apizr_mcp-0.4.6-py3-none-any.whl |
|---|---|
| Size | 28.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8171bec35de3a5003c565e63ad30c6b190d8cb69100c5a21b11df21c4f693eb0
|
|
BLAKE2b-256 checksum How to use checksums |
77afabb8fc62e39f03f0b28afe1ca8b6bb52f399adbf2612458c7922ae06ab1b
|
| 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 19, 2026.
Transparency logSecurity for outerspace-apizr-mcp 0.4.6
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
Both files in this release have been uploaded with provenance metadata.
Attestation for outerspace_apizr_mcp-0.4.6.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 19, 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.
