MCP Podman
PYPI · MCP-PODMAN-CRUNCHTOOLS
MCP server for Podman container management via the Podman REST API
Available components
Last scanned (36 minutes ago)
Scores higher than 95% of PyPI servers
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to crunchtools/mcp-podman). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1131 tokens (~37/item across 30 items; 30 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 97% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "container_kill_tool" implies "kill" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −3
- Stability: pass → 0.83 functional
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/mcp-podman-crunchtools@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | crunchtools/mcp-podman |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/crunchtools/mcp-podman/.github/workflows/publish.yml@refs/tags/v0.1.1 |
| Rekor log index | 1822066351 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:9b82c428f583a644d762d7b6bbf373213b98db1da7a294353c86e9eca2de5f34 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
container_create_tool Container Create Tool ~87
Create a new container.
| Name | Type | Req | Description |
|---|---|---|---|
| command | – | – | Command to run |
| env | – | – | Environment variables |
| image | string | yes | Container image (e.g. "registry.access.redhat.com/ubi9/ubi:latest") |
| labels | – | – | Container labels |
| name | – | – | Container name |
| volumes | – | – | Volume mounts (format: "host_path:container_path[:options]") |
Structured output declared, but exposes no named fields.
No examples provided.
container_inspect_tool Container Inspect Tool ~28
Get detailed information about a container.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Container name or ID |
Structured output declared, but exposes no named fields.
No examples provided.
container_kill_tool Container Kill Tool ~43
Send a signal to a container.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Container name or ID |
| signal | string | – | Signal to send (default: SIGTERM) |
Structured output declared, but exposes no named fields.
No examples provided.
container_list_tool Container List Tool ~61
List containers.
| Name | Type | Req | Description |
|---|---|---|---|
| all_containers | boolean | – | Show all containers (default shows only running) |
| filters | – | – | Filter by key/value pairs (e.g. {"name": ["myapp"]}) |
| limit | – | – | Maximum number of containers to return |
Structured output declared, but exposes no named fields.
No examples provided.
container_logs_tool Container Logs Tool ~78
Get container logs.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Container name or ID |
| since | – | – | Show logs since timestamp (e.g. "2024-01-01T00:00:00Z") |
| tail | – | – | Number of lines from the end of the logs |
| timestamps | boolean | – | Add timestamps to each log line |
Structured output declared, but exposes no named fields.
No examples provided.
container_prune_tool Container Prune Tool ~15
Remove all stopped containers.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
container_restart_tool Container Restart Tool ~41
Restart a container.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Container name or ID |
| timeout | integer | – | Seconds to wait before killing (default: 10) |
Structured output declared, but exposes no named fields.
No examples provided.
container_rm_tool Container Rm Tool ~47
Remove a container.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Force removal of running container |
| name | string | yes | Container name or ID |
| volumes | boolean | – | Remove associated anonymous volumes |
Structured output declared, but exposes no named fields.
No examples provided.
container_start_tool Container Start Tool ~25
Start a stopped container.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Container name or ID |
Structured output declared, but exposes no named fields.
No examples provided.
container_stats_tool Container Stats Tool ~26
Get container resource usage statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Container name or ID |
Structured output declared, but exposes no named fields.
No examples provided.
container_stop_tool Container Stop Tool ~42
Stop a running container.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Container name or ID |
| timeout | integer | – | Seconds to wait before killing (default: 10) |
Structured output declared, but exposes no named fields.
No examples provided.
container_top_tool Container Top Tool ~44
List processes running inside a container.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Container name or ID |
| ps_args | – | – | Arguments to pass to ps (e.g. "aux") |
Structured output declared, but exposes no named fields.
No examples provided.
image_inspect_tool Image Inspect Tool ~31
Get detailed information about an image.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Image name, tag, or ID |
Structured output declared, but exposes no named fields.
No examples provided.
image_list_tool Image List Tool ~33
List images.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | – | – | Filter by key/value pairs (e.g. {"reference": ["ubi9"]}) |
Structured output declared, but exposes no named fields.
No examples provided.
image_prune_tool Image Prune Tool ~14
Remove unused images.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
image_pull_tool Image Pull Tool ~41
Pull an image from a registry.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | Image reference (e.g. "quay.io/crunchtools/rotv:latest") |
Structured output declared, but exposes no named fields.
No examples provided.
image_rm_tool Image Rm Tool ~40
Remove an image.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Force removal even if in use |
| name | string | yes | Image name, tag, or ID |
Structured output declared, but exposes no named fields.
No examples provided.
network_inspect_tool Network Inspect Tool ~28
Get detailed information about a network.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Network name or ID |
Structured output declared, but exposes no named fields.
No examples provided.
network_list_tool Network List Tool ~22
List networks.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | – | – | Filter by key/value pairs |
Structured output declared, but exposes no named fields.
No examples provided.
pod_create_tool Pod Create Tool ~62
Create a new pod.
| Name | Type | Req | Description |
|---|---|---|---|
| infra | boolean | – | Create an infra container (default: True) |
| labels | – | – | Pod labels |
| name | string | yes | Pod name |
| share | – | – | Namespaces to share (ipc, net, uts, pid) |
Structured output declared, but exposes no named fields.
No examples provided.
pod_inspect_tool Pod Inspect Tool ~28
Get detailed information about a pod.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Pod name or ID |
Structured output declared, but exposes no named fields.
No examples provided.
pod_list_tool Pod List Tool ~33
List pods.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | – | – | Filter by key/value pairs (e.g. {"name": ["mypod"]}) |
Structured output declared, but exposes no named fields.
No examples provided.
pod_restart_tool Pod Restart Tool ~28
Restart a pod and all its containers.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Pod name or ID |
Structured output declared, but exposes no named fields.
No examples provided.
pod_rm_tool Pod Rm Tool ~40
Remove a pod and all its containers.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Force removal of running pod |
| name | string | yes | Pod name or ID |
Structured output declared, but exposes no named fields.
No examples provided.
pod_start_tool Pod Start Tool ~28
Start a pod and all its containers.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Pod name or ID |
Structured output declared, but exposes no named fields.
No examples provided.
pod_stop_tool Pod Stop Tool ~45
Stop a pod and all its containers.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Pod name or ID |
| timeout | integer | – | Seconds to wait before killing (default: 10) |
Structured output declared, but exposes no named fields.
No examples provided.
system_df_tool System Df Tool ~15
Get Podman disk usage.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
system_info_tool System Info Tool ~15
Get Podman system information.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
volume_inspect_tool Volume Inspect Tool ~26
Get detailed information about a volume.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Volume name |
Structured output declared, but exposes no named fields.
No examples provided.
volume_list_tool Volume List Tool ~22
List volumes.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | – | – | Filter by key/value pairs |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the MCP Podman server?
MCP Podman runs locally as a PyPI package, launched with uvx mcp-podman-crunchtools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-podman-crunchtools
claude mcp add crunchtools-podman -- uvx mcp-podman-crunchtools
What is the MCP Podman server?
MCP Podman is listed in the public MCP registry as io.github.crunchtools/podman. MCP server for Podman container management via the Podman REST API. This page covers its PyPI package (mcp-podman-crunchtools).
Is the MCP Podman server safe to use?
MCP Podman scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Podman server expose?
MCP Podman exposes 30 tools: container_list_tool, container_inspect_tool, container_start_tool, container_stop_tool, container_restart_tool, and 25 more. Their descriptions and schemas cost roughly 1,088 tokens of context every time the server is loaded.
Is the MCP Podman server still maintained?
MCP Podman is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP Podman server under?
MCP Podman declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.