outerspace-apizr-mcp
This checkout prepares the coordinated 0.4.5 candidate, not a published release. The current public stable baseline remains 0.4.4.
Analyze a local Python project from an MCP client without executing its functions.
Default mode exposes exactly three read-only tools. The published 0.4.2 version also supports opt-in
status/run/resume for an existing
delivery request selected by the operator with --delivery-request. Clients
cannot choose operational paths, credentials or keys. Existing per-operation
grants remain required; delivery uses the shared coordinator and may mutate
registry/proof state.
This optional Apizr plugin runs in its own Python environment. Use the installation guide to choose the matching catalog profile and verified target artifacts. The release record describes the functionality and validation for Apizr 0.4.4.
Installation does not activate a plugin or authorize its operations. Enable the chosen version explicitly and supply the required operator policy. Development locks, activations and permissions are not migrated automatically.
Registry installation (0.4.5 candidate)
The outerspace-apizr-mcp command delegates to apizr mcp serve. Follow the short
Registry installation guide
to create/select the project file, review an explicit analysis policy, and prepare
the separate managed plugin store. Supply their absolute paths through the three
required arguments --project, --operator-policy and --plugins-dir.
Install and activate the matching MCP plugin
in that separate store first. Installing this launcher through a registry client
does not install or activate the governed plugin, grant access to a project, or
enable delivery. Startup retains the existing admission checks and isolated
plugin interpreter. No hosted endpoint is provided.
The repository's server.json describes the future 0.4.5 listing. Registry
publication is separate from package publication; neither is performed by this
candidate. The prepared MCPB wrapper uses the same explicit inputs and admission
checks for later Smithery submission; no hosted endpoint or implicit delivery is
introduced. Use published 0.4.4 core/plugin versions together until release.
See the plugin guide. Python 3.11–3.14. GPL-3.0-or-later; the full license is included.
1 maintainer
Metadata
1 maintainer
Release files for outerspace-apizr-mcp 0.4.5
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.5.tar.gz | 25.6 kB | With provenance | Details for outerspace_apizr_mcp-0.4.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| outerspace_apizr_mcp-0.4.5-py3-none-any.whl | Python 3 | none | any | Details for outerspace_apizr_mcp-0.4.5-py3-none-any.whl |
Total release size: 53.4 kB
Release files / outerspace_apizr_mcp-0.4.5.tar.gz
| Download URL | outerspace_apizr_mcp-0.4.5.tar.gz |
|---|---|
| Size | 25.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a55c23b782b434f8052577ae76592b33033415c1acd5356c9031bd83b730f3a2
|
|
BLAKE2b-256 checksum How to use checksums |
628bde41278dcaa6ba60961e90bc2480b0b9342a6edf787649af373244e63e32
|
| 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 11, 2026.
Transparency logRelease files / outerspace_apizr_mcp-0.4.5-py3-none-any.whl
| Download URL | outerspace_apizr_mcp-0.4.5-py3-none-any.whl |
|---|---|
| Size | 27.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
06311b46195f38f75ee2f4b39d7ac49c83b9b81da4c4abcc908c8753802ee11d
|
|
BLAKE2b-256 checksum How to use checksums |
9a545ad8a4df9c2f1fc218a8a3d9cc0209a2755c3659c2b7b0c4fb2aa6d2f6bf
|
| 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 11, 2026.
Transparency logSecurity for outerspace-apizr-mcp 0.4.5
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.5.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 11, 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.
