Podman Crunchtools MCP Server
mcp-podman-crunchtools
PyPI
v0.2.2
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 2.1 = 98. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
2. Client adoption risk — 98 − 5 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| ✓ | capability blast radius (minimal) — client exposure if the model is manipulated |
| −5 | publisher verification (unlocatable) — no provenance and no public repository to inspect |
| ✓ | inspection depth (source) — how much of the target the scan could see |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Package has no source repositoryMTC-SUP-011
"mcp-podman-crunchtools" declares no repository URL, so its published artifact cannot be compared against reviewable source.
Fix: Prefer packages that link to public, reviewable source.
Location: package mcp-podman-crunchtools
Tools 36
Each tool and what it can reach — statically extracted from the published source.
container_create_toolno sensitive capabilitycontainer_inspect_toolno sensitive capabilitycontainer_kill_toolno sensitive capabilitycontainer_list_toolno sensitive capabilitycontainer_logs_toolno sensitive capabilitycontainer_prune_toolno sensitive capabilitycontainer_restart_toolno sensitive capabilitycontainer_rm_toolno sensitive capabilitycontainer_start_toolno sensitive capabilitycontainer_stats_toolno sensitive capabilitycontainer_stop_toolno sensitive capabilitycontainer_top_toolno sensitive capabilityimage_inspect_toolno sensitive capabilityimage_list_toolno sensitive capabilityimage_prune_toolno sensitive capabilityimage_pull_toolno sensitive capabilityimage_rm_toolno sensitive capabilitynetwork_inspect_toolno sensitive capabilitynetwork_list_toolno sensitive capabilitypod_create_toolno sensitive capabilitypod_inspect_toolno sensitive capabilitypod_list_toolno sensitive capabilitypod_restart_toolno sensitive capabilitypod_rm_toolno sensitive capabilitypod_start_toolno sensitive capabilitypod_stop_toolno sensitive capabilityservice_list_toolno sensitive capabilityservice_logs_toolno sensitive capabilityservice_restart_toolno sensitive capabilityservice_start_toolno sensitive capabilityservice_status_toolno sensitive capabilityservice_stop_toolno sensitive capabilitysystem_df_toolno sensitive capabilitysystem_info_toolno sensitive capabilityvolume_inspect_toolno sensitive capabilityvolume_list_toolno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (36 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.2 latest |
A 93/100 | 1 | 1.8.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-podman-crunchtools --online --registry pypiMore in API Development
Security scan results for the Admin MCP server.
Security scan results for the Assessment MCP server.
Security scan results for the Base MCP server.
Security scan results for the Bling MCP server.
Security scan results for the Blogger MCP server.
Security scan results for the Brilliant Directories MCP server.