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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago