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/harryhazza77/aws-safe-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/harryhazza77/aws-safe-mcp/aws)<a href="https://agentmods.dev/mcp/harryhazza77/aws-safe-mcp/aws"><img src="https://agentmods.dev/badge/mcp/harryhazza77/aws-safe-mcp/aws/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/harryhazza77/aws-safe-mcp/aws"><img src="https://agentmods.dev/badge/mcp/harryhazza77/aws-safe-mcp/aws.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
aws 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 8d 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
{
"aws": {
"command": "uvx",
"args": [
"--from",
"/path/to/aws-sdk-mcp",
"aws-safe-mcp",
"--profile",
"dev",
"--region",
"eu-west-2",
"--readonly",
"--config",
"~/.config/aws-safe-mcp/config.yaml"
]
}
}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.
- 8d ago First seen · 17 lines scan A 279a416526d0
aws is an MCP server published in the GitHub repository harryhazza77/aws-safe-mcp (0 stars, last pushed 3mo 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
mcp-cloudwatch-explorer
MCP server "mcp-cloudwatch-explorer" as configured in sarteta/mcp-cloudwatch-explorer. Runs locally from the mcp-cloudwatch-explorer Python package.
cloudwatch-appsignals
MCP server "cloudwatch-appsignals" as configured in awslabs/mcp. Runs locally from the awslabs.cloudwatch-applicationsignals-mcp-server@latest Python package. Needs 1 environment variable to run.
cloudwatch
MCP server "cloudwatch" as configured in awslabs/mcp. Runs locally from the awslabs.cloudwatch-mcp-server@latest Python package. Needs 1 environment variable to run.
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.
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…
cloud-finops
MCP server exposing the OptimNow Cloud FinOps skill (reference library + named-pattern playbooks) as queryable tools. Runs locally from the cloud-finops-mcp Python package.