Cloud Audit MCP Server
cloud-audit
PyPI
v2.4.0
Published by gebalamariusz — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:
| Points | What was found | Category |
|---|---|---|
| −33 | Hardcoded AWS access key id in server code ×2 MTC-SRC-008 | exfiltration |
Grade capped: 2 confirmed high findings → grade capped at D. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.
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 the deduction.
Findings 3
high Reads a sensitive credential path or dumps the environment (src/cloud_audit/cli.py)MTC-SRC-006
In the server's implementation (`src/cloud_audit/cli.py:36`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: .aws/credentials
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/cloud_audit/cli.py
high Hardcoded AWS access key id in server code (scripts/generate_report_screenshot.py)MTC-SRC-008
A live-looking AWS access key id is hardcoded in `scripts/generate_report_screenshot.py:83`. Secrets in source ship to everyone who installs the package and are a direct credential leak.
Evidence: AWS access key id: AKIA…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server scripts/generate_report_screenshot.py
high Hardcoded AWS access key id in server code (src/cloud_audit/providers/aws/checks/iam.py)MTC-SRC-008
A live-looking AWS access key id is hardcoded in `src/cloud_audit/providers/aws/checks/iam.py:89`. Secrets in source ship to everyone who installs the package and are a direct credential leak.
Evidence: AWS access key id: AKIA…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server src/cloud_audit/providers/aws/checks/iam.py
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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 |
|---|---|---|---|---|
v2.4.0 latest |
D 67/100 | 3 | 1.5.0 | 2026-07-22 |
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 cloud-audit --online --registry pypiMore in Security & Testing
Security scan results for the 1claw MCP server.
Security scan results for the 1password MCP server.
Security scan results for the 1password MCP server.
Security scan results for the A11y MCP server.
Security scan results for the A11y Tools MCP server.
Security scan results for the Abuseipdb MCP server.