Kloudle Cloud Security Scanner

io.github.KloudlePublished by GitHub account Kloudlev0.1.1Updated Oct 24, 2026

AWS cloud security scanners for AI agents — S3, IAM, EC2, EKS, RDS, CloudTrail, CloudWatch Logs

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant run AWS cloud security scans across services such as S3, IAM, EC2, EKS, RDS, CloudTrail and CloudWatch Logs.

What you can do
This remote MCP server exposes AWS cloud security scanning to an AI assistant. According to its registry description, it covers S3, IAM, EC2, EKS, RDS, CloudTrail and CloudWatch Logs. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Consider it when you want an assistant to help review AWS security posture across storage, identity, compute, Kubernetes, databases and audit or log data. It is aimed at cloud security checks rather than general AWS administration.
Requirements
A remote streamable HTTP endpoint at mcp.kloudle.dev; no local package or runtime is declared. The manifest declares no authentication, environment variables or headers, but access to AWS account data would normally require credentials or authorization.
Before you install
The server is described as scanning AWS accounts, so it may read sensitive cloud configuration, identity and log data. The manifest declares no authentication, which is unusual for a service reaching into cloud accounts; confirm how access and authorization are actually handled before connecting it to a real account.

Installation

In SourceWeft

  1. Open Kloudle Cloud Security Scanner in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Kloudle%2Fcloud-security-scanner/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "kloudle-cloud-security-scanner": {
      "type": "http",
      "url": "https://mcp.kloudle.dev/mcp"
    }
  }
}

Tools

2

get

Get full metadata, SHA256 hash, download URL, and ready-to-run shell command for a Kloudle scanner binary. Pass args to get a complete command; omit for a template with placeholders.

Parametersargsnamerequired

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.