MCP Server 0378c546

MCP安全风控

提供方 rad-security

安全风控 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude DesktopClaude
查看接入方式

RAD Security MCP Server是一款为Kubernetes和云环境提供AI驱动的安全洞察的模型上下文协议服务器。

一句话选型结论

按资料字段整理

MCP Server 0378c546 属于安全风控类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude Desktop、Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类安全风控 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 6 仓库热度,无公开仓库时显示未标注
工具数 41 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

安全风控
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量41暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

Kubernetes安全TypeScript混合部署云安全AI安全分析容器安全安全协议

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
docker run \

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Docker,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 41 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
资产与漏洞排查

盘点资产、扫漏洞、看暴露面。

日志与审计

汇总日志、查异常行为。

合规检查

按规则检查配置与权限是否合规。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 41 个工具,覆盖面较广,能满足多种调用。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在安全风控场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Server 0378c546当前 41 stdio · 本地进程 本地部署 有 2026-05-17
Cyber Strike AI 75 未标注 未标注 无 2026-05-17
mcp-for-beginners 未标注 stdio · 本地进程 本地部署 有 2026-04-13
casdoor 未标注 stdio · 本地进程 本地部署 有 2026-04-12
kubeshark 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Modelcontextprotocol C22988b0 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

安全风控
字段来自项目仓库与公开索引,中文说明由本站标注
提供方rad-security上游标注的维护方 rad-security
分类安全风控本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Docker本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

12.0 KB
来自项目仓库与上游目录的原文,未做删改

RAD Security MCP Server

A Model Context Protocol (MCP) server for RAD Security, providing AI-powered security insights for Kubernetes and cloud environments.

Connect (hosted — recommended)

RAD Security runs the MCP server for you, so most users don't need to install or host anything. Point your MCP client at the hosted endpoint and authenticate with your RAD Security credentials.

  • Endpoint: https://api.rad.security/mcp/ — note the trailing slash.
  • Transport: Streamable HTTP.
  • Authentication: send your credential in the Authorization header:Authorization: Bearer <access_key_id>:<secret_key>:<account_id>

and are a RAD Security API access key (create one in the RAD Security console); `` is your account ID. The server authenticates every request against the RAD Security API — no credentials are stored server-side.

> A short-lived form Bearer ory_st_: also works, but session tokens expire — prefer an access key for anything long-lived (e.g. Slack / Claude Tag).

Claude Code```bash

claude mcp add --transport http rad-security https://api.rad.security/mcp/ \
--header "Authorization: Bearer <access_key_id>:<secret_key>:<account_id>"


### OpenAI Codex CLI

`~/.codex/config.toml`:```toml
[mcp_servers.rad-security]
url = &quot;https://api.rad.security/mcp/&quot;
http_headers = { &quot;Authorization&quot; = &quot;Bearer &lt;access_key_id&gt;:&lt;secret_key&gt;:&lt;account_id&gt;&quot; }

Or via the CLI, keeping the secret in an env var (export RAD_MCP_TOKEN=::):```bash
codex mcp add rad-security --url https://api.rad.security/mcp/ --bearer-token-env-var RAD_MCP_TOKEN


### Cursor

`.cursor/mcp.json`:```json
{
  &quot;mcpServers&quot;: {
    &quot;rad-security&quot;: {
      &quot;type&quot;: &quot;http&quot;,
      &quot;url&quot;: &quot;https://api.rad.security/mcp/&quot;,
      &quot;headers&quot;: {
        &quot;Authorization&quot;: &quot;Bearer &lt;access_key_id&gt;:&lt;secret_key&gt;:&lt;account_id&gt;&quot;
      }
    }
  }
}

VS Code (GitHub Copilot)

.vscode/mcp.json — note the wrapper key is servers, not mcpServers:```json
{
"servers": {
"rad-security": {
"type": "http",
"url": "https://api.rad.security/mcp/",
"headers": {
"Authorization": "Bearer <access_key_id>:<secret_key>:<account_id>"
}
}
}
}


### Gemini CLI

`~/.gemini/settings.json` — note the URL field is `httpUrl` (not `url`):```json
{
  &quot;mcpServers&quot;: {
    &quot;rad-security&quot;: {
      &quot;httpUrl&quot;: &quot;https://api.rad.security/mcp/&quot;,
      &quot;headers&quot;: {
        &quot;Authorization&quot;: &quot;Bearer &lt;access_key_id&gt;:&lt;secret_key&gt;:&lt;account_id&gt;&quot;
      }
    }
  }
}

Cline

cline_mcp_settings.json — note type must be exactly streamableHttp (camelCase):```json
{
"mcpServers": {
"rad-security": {
"type": "streamableHttp",
"url": "https://api.rad.security/mcp/",
"headers": {
"Authorization": "Bearer <access_key_id>:<secret_key>:<account_id>"
}
}
}
}


### Windsurf

`~/.codeium/windsurf/mcp_config.json` — note the URL field is `serverUrl`:```json
{
  &quot;mcpServers&quot;: {
    &quot;rad-security&quot;: {
      &quot;serverUrl&quot;: &quot;https://api.rad.security/mcp/&quot;,
      &quot;headers&quot;: {
        &quot;Authorization&quot;: &quot;Bearer &lt;access_key_id&gt;:&lt;secret_key&gt;:&lt;account_id&gt;&quot;
      }
    }
  }
}

Other clients

Most MCP clients accept a remote Streamable HTTP server with a URL and an Authorization header — only the field names differ. Keep the trailing slash on the URL in every case.

Client Config location URL field Transport marker Header field
Claude Code claude mcp add positional arg --transport http --header
OpenAI Codex CLI ~/.codex/config.toml url inferred http_headers / bearer_token_env_var
Cursor .cursor/mcp.json url type: &quot;http&quot; headers
VS Code .vscode/mcp.json (servers) url type: &quot;http&quot; headers
Gemini CLI ~/.gemini/settings.json httpUrl inferred headers
Cline cline_mcp_settings.json url type: &quot;streamableHttp&quot; headers
Windsurf ~/.codeium/windsurf/mcp_config.json serverUrl inferred headers

Claude.ai / Claude Desktop / Claude Tag (Slack)

These surfaces add remote MCP servers as connectors, which use their own credential settings rather than a raw request header. Add https://api.rad.security/mcp/ as a custom connector, then supply the bearer credential through the connector's settings:

  • Claude Tag (Slack): attach the server as a plugin whose .mcp.json points at the endpoint, and add the bearer credential on the Access bundle's Credentials tab. See Claude Tag — connect a custom MCP server.
  • Claude.ai / Desktop: add it under Settings → Connectors; see custom connectors.

Test it (MCP Inspector or curl)```bash

npx @modelcontextprotocol/inspector

Transport: Streamable HTTP

URL: https://api.rad.security/mcp/ (trailing slash)

Custom headers: { "Authorization": "Bearer <access_key_id>:<secret_key>:<account_id>" }

``````bash
curl -H "authorization: Bearer <access_key_id>:<secret_key>:<account_id>" \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-X POST https://api.rad.security/mcp/ \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'


### Scoping the tools an agent sees

By default a connection gets every toolkit. To give an agent a smaller set — less context/token overhead, and least privilege — add a scoping header to that connection alongside `Authorization`. The subset is enforced: an out-of-scope tool is hidden from `tools/list` **and** rejected if called.

| Header | Effect |
| --- | --- |
| `X-Rad-Toolkits: findings, images` | only these toolkits |
| `X-Rad-Exclude-Toolkits: workflows` | every toolkit except these |
| `X-Rad-Readonly: true` | only read-only tools (drops the write tools) |

Toolkits: `containers`, `clusters`, `audit`, `images`, `kubeobject`, `runtime`, `findings`, `inbox`, `workflows`, `knowledge_base`, `radql`, `dashboards`, `integrations`. All are enabled by default — narrow with the headers above, and use `X-Rad-Readonly` when you want to exclude every write tool.

Example — a read-only findings/images agent (any client that supports headers; Cursor shown):```json
{
  &quot;mcpServers&quot;: {
    &quot;rad-security-findings&quot;: {
      &quot;type&quot;: &quot;http&quot;,
      &quot;url&quot;: &quot;https://api.rad.security/mcp/&quot;,
      &quot;headers&quot;: {
        &quot;Authorization&quot;: &quot;Bearer &lt;access_key_id&gt;:&lt;secret_key&gt;:&lt;account_id&gt;&quot;,
        &quot;X-Rad-Toolkits&quot;: &quot;findings, images&quot;,
        &quot;X-Rad-Readonly&quot;: &quot;true&quot;
      }
    }
  }
}

In Claude Code, pass an extra --header:```bash
claude mcp add --transport http rad-security https://api.rad.security/mcp/ \
--header "Authorization: Bearer <access_key_id>:<secret_key>:<account_id>" \
--header "X-Rad-Toolkits: findings, images"


## Features

All tools require authentication and an account in RAD Security. The hosted endpoint exposes every toolkit below by default; scope a client down with `X-Rad-Toolkits` / `X-Rad-Exclude-Toolkits`, or drop all write tools with `X-Rad-Readonly: true`.

- Account Inventory
  - List clusters and their details

- Containers Inventory
  - List containers and their details

- Security Findings
  - List and analyze security findings
  - Update the status of a security finding

- Runtime Security
  - Get process trees of running containers
  - Get runtime baselines of running containers
  - Analyze process behavior of running containers

- Audit
  - List who shelled into a pod

- Images and Vulnerabilities
  - Get SBOMs
  - List images and their vulnerabilities
  - Get top vulnerable images
  - Ignore / unignore CVEs and list active CVE dispositions

- Kubernetes Objects
  - Get details of a specific Kubernetes resource
  - List Kubernetes resources

- Inbox
  - List inbox items and their details
  - Mark an inbox item as a false positive

- Automations (`workflows`)
  - List automations, runs and schedules
  - Get automation and run details
  - Run an automation
  - Create and update automations, and add cron schedules

  &gt; &quot;Automation&quot; is the product name users see; &quot;workflow&quot; is the underlying Windmill object the
  &gt; API and tool names use. They are the same thing.

- Knowledge Base
  - Search the knowledge base
  - List collections and documents
  - Run structured queries against a document

- Dashboards
  - List dashboards and get their details
  - List and get dashboard and widget templates
  - Create a dashboard, and update one in place (omitted fields are left unchanged, so a small
    edit does not require resending the whole dashboard)

- Integrations
  - List external integrations

- RadQL (Advanced Querying)
  - List available data types for querying (containers, findings, kubernetes_resources, etc.)
  - Get schema/metadata for specific data types
  - List possible values for filter fields
  - Execute RadQL queries with filtering, searching, and aggregations
  - Build queries programmatically from structured conditions
  - Execute multiple queries in parallel

## Self-hosting

Prefer to run the server yourself — for example an air-gapped environment, data-residency requirements, or if you don&#x27;t want to route through the hosted gateway? It&#x27;s published to npm and as a container image.

### Prerequisites

- Node.js 20.x or higher

### Credentials

Provide your RAD Security credentials via environment variables:```bash
RAD_SECURITY_ACCESS_KEY_ID=&quot;your_access_key&quot;
RAD_SECURITY_SECRET_KEY=&quot;your_secret_key&quot;
RAD_SECURITY_ACCOUNT_ID=&quot;your_account_id&quot;

# Optional: fetched automatically from the account if not set
RAD_SECURITY_TENANT_ID=&quot;your_tenant_id&quot;

npx (stdio) — e.g. Claude Desktop```json

{
"mcpServers": {
"rad-security": {
"command": "npx",
"args": ["-y", "@rad-security/mcp-server"],
"env": {
"RAD_SECURITY_ACCESS_KEY_ID": "<your-access-key-id>",
"RAD_SECURITY_SECRET_KEY": "<your-secret-key>",
"RAD_SECURITY_ACCOUNT_ID": "<your-account-id>"
}
}
}
}


### Docker (Streamable HTTP)```bash
docker build -t rad-security/mcp-server .
docker run \
  -e TRANSPORT_TYPE=streamable \
  -e RAD_SECURITY_ACCESS_KEY_ID=your_access_key \
  -e RAD_SECURITY_SECRET_KEY=your_secret_key \
  -e RAD_SECURITY_ACCOUNT_ID=your_account_id \
  -p 3000:3000 \
  rad-security/mcp-server

Toolkit filtering

Control which toolkits a self-hosted server exposes:

  • INCLUDE_TOOLKITS: comma-separated list of toolkits to include (only these are enabled).
  • EXCLUDE_TOOLKITS: comma-separated list of toolkits to exclude (all others are enabled). Ignored if INCLUDE_TOOLKITS is set.

Available toolkits: containers, clusters, audit, images, kubeobject, runtime, findings, inbox, workflows, knowledge_base, radql, dashboards, integrations. All are enabled by default.```bash

Only the workflows toolkit

INCLUDE_TOOLKITS="workflows"

Everything except runtime

EXCLUDE_TOOLKITS="runtime"


### Multi-tenant (per-request auth)

`MCP_AUTH_MODE` controls how a streamable HTTP deployment authenticates inbound requests — this is what the hosted endpoint uses:

- `MCP_AUTH_MODE=env` (default) — every session uses the `RAD_SECURITY_*` environment credentials. Single-tenant, and **unauthenticated at the HTTP layer**, so it must not be reachable from untrusted networks.
- `MCP_AUTH_MODE=header` — every request must carry its own credential in the `Authorization` header (the `Bearer ::` form above); a missing or malformed header is rejected with `401`. Only supported with `TRANSPORT_TYPE=streamable`. `RAD_SECURITY_API_URL` is taken from server config, not the caller.```bash
docker run \
  -e TRANSPORT_TYPE=streamable \
  -e MCP_AUTH_MODE=header \
  -e RAD_SECURITY_API_URL=https://api.rad.security \
  -p 3000:3000 \
  rad-security/mcp-server

> The SSE transport (TRANSPORT_TYPE=sse) is deprecated in favor of Streamable HTTP and uses env credentials only.

Development```bash

Install dependencies

npm install

Run type checking

npm run type-check

Run linter

npm run lint

Build

npm run build
```

License

MIT License - see the LICENSE file for details

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
MCP Server 0378c546 怎么安装?

在客户端按下面的安装命令接入:docker run \。装完在客户端配置里引用同一个包或端点。

MCP Server 0378c546 怎么在 Claude Desktop、Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP Server 0378c546 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP Server 0378c546 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

MCP Server 0378c546 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

MCP Server 0378c546 能提供哪些能力?

资料显示约 41 个工具;能力标签包括 安全协议、TypeScript、Claude。具体工具清单以官方文档为准。

MCP Server 0378c546 需要什么运行环境?

运行时为 Docker;属于本地进程,需要在本机装好运行环境。

MCP Server 0378c546 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。