RAD Security MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is RAD Security MCP Server?

RAD Security MCP Server is a Model Context Protocol (MCP) server designed to provide AI-powered security insights for Kubernetes and cloud environments.

how to use RAD Security MCP Server?

To use the RAD Security MCP Server, install it via npm, set the required environment variables, and run it either in a local environment or as a Docker container.

key features of RAD Security MCP Server?

  • Account Inventory: List clusters and their details.
  • Containers Inventory: List containers and their details.
  • Security Findings: Analyze security findings.
  • Runtime Security: Monitor running containers and analyze their behavior.
  • Network Security: Track network connections and analyze patterns.
  • Identity and Access: Manage identities and access details.
  • Audit: Monitor access to pods.
  • Cloud Security: Monitor cloud resources and compliance.
  • Images: Analyze vulnerabilities in images.
  • Kubernetes Objects: Manage and monitor Kubernetes resources.
  • CVEs: Access and analyze Common Vulnerabilities and Exposures.

use cases of RAD Security MCP Server?

  1. Monitoring security in Kubernetes environments.
  2. Analyzing vulnerabilities in cloud resources.
  3. Managing identities and access in cloud applications.
  4. Auditing access to sensitive resources.

FAQ from RAD Security MCP Server?

  • What are the prerequisites for using the MCP server?

You need Node.js 20.x or higher and the required environment variables set up.

  • Can I use the MCP server without authentication?

Yes, some operations like listing CVEs can be performed without authentication.

  • Is there a Docker version available?

Yes, you can run the MCP server as a Docker container.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
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