Is Podman MCP Server safe to use?

Podman MCP Server has an HVTrust score of 65.3/100 (Grade B), ranked #521 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Podman MCP Server?

Podman MCP Server scores 65.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 85 GitHub stars and is categorized under MCP Servers.

Podman MCP Server

Repository

Model Context Protocol (MCP) server for container runtimes (Podman and Docker)

MCP Servers Go Listed Apache-2.0

Is Podman MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.7 / 10

Provenance Attested

Signed commits 91%

Last push 81d ago

Advisories None known

Compare Podman MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Podman MCP Server scores 65.3/100 (Grade B), ranked #521 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.7/10; 91% of recent commits are signed; no published advisory affects its latest release (podman-mcp-server, podman-mcp-server); last pushed 2026-08-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Podman MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 3.7 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +11.1 → 76.4 B · #142 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Podman MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/manusa/podman-mcp-server, Apache-2.0, last pushed 2026-08-21. 91% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 3.7/10 (scanned Oct 25, 2026, refresh pending). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 2

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages Partly attested
- npm podman-mcp-server Source link points back to this repo Build provenance attested
- PyPI podman-mcp-server Source link points back to this repo No build attestation
What you install today No known advisories

Latest releases checked: podman-mcp-server 0.0.15, podman-mcp-server 0.0.15. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-08-27 OSSF Scorecard: 4.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Podman MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Podman MCP Server compares in MCP Servers

#298 Umbraco CMS MCP Dev 65.4 +0.1
#299 Redmine MCP Server 65.4 +0.1
#300 Podman MCP Server 65.3 this agent
#301 Home Assistant MCP 65.3 ±0
#302 Persistent Project Context for xAI Grok 65.2 −0.1

Bars show each HVTrust score; the tick marks Podman MCP Server’s 65.3.

Where the 65.3 comes from

HVTrust dimensions vs the MCP Servers average

65.3 / 100 · 100.0% confidence

Podman MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

16.7 / 25

5.9 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

11.6 / 17

0.7 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

6.6 / 20

5.6 below avg 12.2

AdoptionLog-scaled stars · package downloads

6.4 / 20

1.2 below avg 7.6

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-11-08

Rank Moved

Rank dropped 91 spots (#419 → #510)

2026-11-06

Rank Moved

Rank rose 14 spots (#435 → #421)

2026-11-05

Rank Moved

Rank rose 20 spots (#455 → #435)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.7/10. Tighten the weakest checks to improve public safety evidence.

Refresh maintenance signals The repo was last pushed 81 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent View MCP Servers Report missing data

31.3

Activity sub-score · out of 100

#300

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-08-21

81 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼8

was #513

Analysis

Activity Inputs

31.3 / 100

StarsRepository reach

11.6 / 30

FreshnessLast push recency

13.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.9 / 20

Common questions about Podman MCP Server

Podman MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Podman MCP Server publish package provenance?

Yes. Podman MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Podman MCP Server have an OpenSSF Scorecard?

Podman MCP Server has an OpenSSF Scorecard score of 3.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Podman MCP Server actively maintained?

Slowing down. Last push was 81 days ago — keep an eye on whether activity resumes.

What license does Podman MCP Server use?

Podman MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Podman MCP Server's commits signed?

91% of the last 100 commits to Podman MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Podman MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Podman MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Podman MCP Server?

For maintainers

HVTrust scores Podman MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-11-08

Rank Moved

Rank dropped 91 spots (#419 → #510)

2026-11-06

Rank Moved

Rank rose 14 spots (#435 → #421)

2026-11-05

Rank Moved

Rank rose 20 spots (#455 → #435)

2026-10-28

Rank Moved

Rank rose 28 spots (#476 → #448)

2026-10-23

Rank Moved

Rank dropped 31 spots (#430 → #461)

2026-10-20

Rank Moved

Rank rose 27 spots (#456 → #429)

2026-10-18

Rank Moved

Rank dropped 13 spots (#441 → #454)

2026-10-17

Rank Moved

Rank dropped 43 spots (#398 → #441)

2026-10-15

Rank Moved

Rank rose 32 spots (#429 → #397)

2026-10-14

Rank Moved

Rank dropped 37 spots (#392 → #429)

2026-10-12

Rank Moved

Rank dropped 10 spots (#384 → #394)

2026-10-09

Rank Moved

Rank dropped 23 spots (#361 → #384)

2026-09-27

Rank Moved

Rank rose 19 spots (#363 → #344)

2026-09-25

Rank Moved

Rank dropped 28 spots (#335 → #363)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 755 spots (#1086 → #331)

2026-09-23

HVTrust Changed

HVTrust up 47.2pts (22.5 → 69.7)

2026-09-22

Newly Listed

First tracked at rank #1086

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 23 spots (#297 → #320)

2026-09-19

Rank Moved

Rank rose 21 spots (#318 → #297)

2026-09-18

Rank Moved

Rank dropped 15 spots (#303 → #318)

2026-09-17

Rank Moved

Rank dropped 29 spots (#274 → #303)

2026-09-14

Rank Moved

Rank rose 18 spots (#287 → #269)

2026-09-13

Rank Moved

Rank dropped 25 spots (#262 → #287)

2026-09-11

Rank Moved

Rank dropped 11 spots (#249 → #260)

2026-09-07

Rank Moved

Rank dropped 15 spots (#219 → #234)

2026-09-05

Rank Moved

Rank dropped 34 spots (#182 → #216)

2026-09-03

Rank Moved

Rank dropped 14 spots (#163 → #177)

2026-08-31

Rank Moved

Rank dropped 21 spots (#133 → #154)

2026-08-27

Scorecard Added

OSSF Scorecard: 4.0/10

2026-08-27

Rank Moved

Rank rose 129 spots (#256 → #127)

2026-08-27

HVTrust Changed

HVTrust up 8.4pts (65.0 → 73.4)

2026-08-26

Rank Moved

Rank dropped 19 spots (#237 → #256)

2026-08-24

Rank Moved

Rank dropped 17 spots (#220 → #237)

2026-08-22

Rank Moved

Rank rose 15 spots (#235 → #220)

2026-08-21

Grade Changed

Trust grade C → B

2026-08-19

Rank Moved

Rank dropped 15 spots (#225 → #240)

2026-08-18

Rank Moved

Rank rose 41 spots (#266 → #225)

2026-08-18

Activity Score Changed

Activity score up 6pts (42 → 48)

2026-08-17

Rank Moved

Rank rose 37 spots (#303 → #266)

2026-08-15

Rank Moved

Rank dropped 13 spots (#292 → #305)

2026-08-13

Rank Moved

Rank dropped 20 spots (#275 → #295)

GitHub → PyPI: podman-mcp-server npm: podman-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/podman-mcp-server.svg)](https://hvtracker.net/agents/podman-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/podman-mcp-server"><img src="https://hvtracker.net/badge/podman-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Podman MCP Server

How Podman MCP Server could raise its score

Chain of custody

Source Signed

Review and release Weak

Published packages Partly attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Podman MCP Server compares in MCP Servers

Where the 65.3 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Podman MCP Server

AI agent surface

Maintain Podman MCP Server?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers