Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/sandraschi/podman-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/sandraschi/podman-mcp/schip-mcp-podman)<a href="https://agentmods.dev/mcp/sandraschi/podman-mcp/schip-mcp-podman"><img src="https://agentmods.dev/badge/mcp/sandraschi/podman-mcp/schip-mcp-podman/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/sandraschi/podman-mcp/schip-mcp-podman"><img src="https://agentmods.dev/badge/mcp/sandraschi/podman-mcp/schip-mcp-podman.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
schip-mcp-podman scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "schip-mcp-podman": { "command": "uvx", "args": [ "schip-mcp-podman" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 8 lines scan A 1ddb3384a867
schip-mcp-podman is an MCP server published in the GitHub repository sandraschi/podman-mcp (1 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
stripe-mcp
MCP server "stripe-mcp" as configured in sandraschi/stripe-mcp. Runs locally from the stripe-mcp Python package.
dockerfile-audit
Hadolint-grade Dockerfile audit — 19 checks: secrets, privileges, supply chain, hygiene. Remote server at unbearable-dev--dockerfile-audit.apify.actor.
sandbox-mcp
General-purpose Python execution sandbox with FastMCP tools, artifact capture, Manim rendering, and web demo workflows. Runs locally from the sandbox-mcp Python package.
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
nexus-mcp
Model Context Protocol server for AI CLI agents. Runs locally from the nexus-mcp Python package.
gitee-mcp
MCP server "gitee-mcp" as configured in sandraschi/gitee-mcp. Runs locally from the gitee-mcp Python package.