Back to Browse

Outerspace Apizr MCP Server

Developer ToolsLow Risk9.7MCP RegistryLocal
Free

Server data from the Official MCP Registry

Python capability compiler: local read-only analysis and explicit MCP/REST exposure planning.

About

Python capability compiler: local read-only analysis and explicit MCP/REST exposure planning.

Security Report

9.7
Low Risk9.7Low Risk

Valid MCP server (4 strong, 1 medium validity signals). No known CVEs in dependencies. ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

16 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-alien6-studio-outerspace-apizr": {
      "args": [
        "outerspace-apizr-mcp"
      ],
      "command": "uvx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

OuterSpace Apizr

Connect selected Python functions to AI agents through MCP, or expose them as REST APIs.

Apizr is an open-source capability compiler: analyze existing Python code, choose which functions are public, generate their interfaces, and define how they execute. Your business logic stays in Python.

Quickstart: make your first MCP and REST calls · The full journey

Follow Install Apizr, then the Quickstart. See the release history for version-specific functionality, compatibility and verified publication. The journey is Python code → discover/select capabilities → expose as REST/MCP → optionally deliver as OCI.

Apizr 0.4.4 adds portable JSON evidence export/verification and a bounded HTTPS check for ambiguous first-publication diagnostics. See the release record and external governance handoff for scope, validation and integration limits. Publication status is recorded in the release history.

Python 3.11–3.14 · GPL-3.0-or-later.

PyPI version CI Security Documentation Python License OuterSpace Apizr MCP server – quality and maintenance score on Glama

Choose your path

Your goalStart here
Expose Python functions as MCP tools or REST endpointsInstall → Quickstart
Analyze a project from an MCP clientInstall the MCP profile → analysis server
Build and deliver a serviceInstall OCI or delivery → OCI and Attest
Initialize and diagnose a project (0.4.2)Safe init, read-only doctor and shell completion
Validate/build in CI (0.4.2)GitHub Action, GitLab component source and apizr ci

The core handles supported static analysis and generation. Generated servers have their own runtime dependencies. Optional plugins live in separate environments; installation, activation and operator authorization are independent decisions.

Expose the functions you choose

Readiness reports whether the available code evidence supports an interface. An exposure policy names the functions you choose to make public. A bundle is the generated server, its contracts and the source needed by those functions. Being ready never makes a function public automatically.

Connect throughStart with
MCP tools for agents and other clientsGenerate MCP and make two calls
REST endpoints for applicationsGenerate REST and send two requests

The generated MCP server calls your selected functions. The separate, Apizr analysis MCP server analyzes repositories and plans exposure; it does not execute their functions.

Choose execution boundaries

Analysis and generation do not execute the project. Starting a generated server and calling its functions does: use trusted source and dependencies. Direct mode runs functions inside the server. Governed mode uses an execution policy to choose a worker and its required limits: a fresh local process or an OCI container per call. Local workers do not isolate the host filesystem or network; containers are not an untrusted-code guarantee.

The direct Quickstart needs no Docker. Read the exposure guide for governed examples and the execution boundaries for their guarantees and limits.

Existing workflows and limits

Single-source inspect, generate rest/mcp and execute remain supported. Apizr 0.4.2 also exports verified REST bundles to Postman, Bruno and Insomnia collections, with deterministic files and safe local regeneration.

The historical pipeline is a separate compatibility path. See the full journey for dependency, resource and exposure limits.

Watch the demo · Architecture · Development and checks · Report an issue · GPL-3.0-or-later

Reviews

No reviews yet

Be the first to review this server!