MCP Cloud Compliance

Created By
uprightsleepya year ago
Conversational cloud security compliance auditing. MCP server enabling natural language queries about AWS security posture via Claude and other AI assistants.
Overview

What is MCP Cloud Compliance?

MCP Cloud Compliance is a server designed for conversational cloud security compliance auditing, enabling users to query AWS security posture using natural language through AI assistants like Claude.

How to use MCP Cloud Compliance?

To use MCP Cloud Compliance, follow these steps:

  1. Build the project using Maven: mvn clean package
  2. Run the server with the command: java -jar target/cloud-compliance-mcp-0.1.0.jar
  3. Configure Claude for Desktop as per the documentation.

Key features of MCP Cloud Compliance?

  • Health check tool for cloud security compliance
  • S3 compliance checking (in progress)
  • IAM policy auditing (in progress)
  • Security group analysis (in progress)

Use cases of MCP Cloud Compliance?

  1. Conducting security audits for AWS environments
  2. Ensuring compliance with NIST and SOC2 standards
  3. Analyzing IAM policies for security vulnerabilities

FAQ from MCP Cloud Compliance?

  • What technologies does MCP Cloud Compliance use?

MCP Cloud Compliance is built using Java and Maven.

  • Is MCP Cloud Compliance free to use?

Yes! MCP Cloud Compliance is open-source and available under the MIT license.

  • What are the system requirements?

You need Java 17+ and Maven 3.6+ to run MCP Cloud Compliance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
uprightsleepy
Star
1
Language
Java
License
MIT license
Category
security

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

3 hours ago