Atmos is an infrastructure runtime that coordinates tools such as Terraform, OpenTofu, Kubernetes, Helm, Packer, Ansible, and containers through consistent commands and configuration. It is for teams running cloud infrastructure on laptops, in CI, or through AI agents across environments and regions. Its catalogue entries provide skills, agents, commands, and other add-ons for Atmos workflows.
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/cloudposse/atmosWrote 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/cloudposse/atmos/stepsecurity)<a href="https://agentmods.dev/mcp/cloudposse/atmos/stepsecurity"><img src="https://agentmods.dev/badge/mcp/cloudposse/atmos/stepsecurity/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/cloudposse/atmos/stepsecurity"><img src="https://agentmods.dev/badge/mcp/cloudposse/atmos/stepsecurity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stepsecurity 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 1mo 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
{
"stepsecurity": {
"type": "http",
"url": "https://agent.api.stepsecurity.io/v1/mcp"
}
}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.
- 1mo ago First seen · 6 lines scan A 3a5f7e8cbe39
stepsecurity is an MCP server published in the GitHub repository cloudposse/atmos (1,406 stars, last pushed today), licensed Apache-2.0. 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-09-03.
Other mcp servers, from other repositories
cloud-audit
Open-source, read-only AWS security scanner. 110 checks across 25 services, 31 attack-chain rules, 64 IAM escalation methods (incl. lateral AssumeRole graph), Proof Mode exploitability verification, data perimeter and Bedrock AgentCore checks, Blast Radius CLI, Threat Feed, What-If simulator, AI-SPM, 6 compliance…
servonaut
Manage AWS, Hetzner, OVH, and custom servers from one TUI — with a built-in AI assistant and MCP server. Runs locally from the servonaut Python package.
trusty-review
MCP server "trusty-review" as configured in bobmatnyc/claude-mpm. Launched with trusty-review serve --stdio. Needs 1 environment variable to run.
trusty-search
MCP server "trusty-search" as configured in bobmatnyc/claude-mpm. Launched with trusty-search serve.
smbcloud-cli
Email infrastructure and authentication for developers: domains, inbox routes, auth apps, deploys. Runs locally from the @smbcloud/cli npm package. Needs 1 environment variable to run.
dokploy-mcp
Dokploy MCP server for Codex, Cursor, and Claude with compact stdio and hosted HTTP modes. Runs locally from the @vibetools/dokploy-mcp npm package. Needs 3 environment variables to run.