AWS cloud security scanners for AI agents — S3, IAM, EC2, EKS, RDS, CloudTrail, CloudWatch Logs
Dev & Codev0.1.1streamable-httpmcp.kloudle.dev
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 139ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2024-11-05, serverInfo kloudle-cloud-security-scanner@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 2 tools e.g. "search"; 2/2 described, 2/2 fully-typed schemas, median description 182 chars |
| latency | 10 / 10 | initialize round-trip 139ms |
| provenance | 5 / 15 | description present; no repository URL; version 0.1.1; namespace io.github.Kloudle does NOT match remote host (expected *.kloudle.github.io) |
Score 90/100 · latency 139ms · 2 tools · auth: open
Claude Code:
claude mcp add --transport http cloud-security-scanner https://mcp.kloudle.dev/mcp
Generic MCP client config:
{ "mcpServers": { "cloud-security-scanner": { "type": "http", "url": "https://mcp.kloudle.dev/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/io.github.Kloudle/cloud-security-scanner · referral link https://mcpqueen.com/go/io.github.Kloudle/cloud-security-scanner (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.Kloudle/cloud-security-scanner)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 17:17 | A | 90 | 139ms |