Bright Security

io.github.NeuraLegion由 GitHub 账号 NeuraLegion 发布v1.0.1更新于 Oct 24, 2026

AI-powered application security testing — scan APIs, discover endpoints, and find vulnerabilities.

已验证SSE可网页运行开发者工具安全与监控

概览

AI 生成的概览

Bright Security 的远程 MCP 服务器让 AI 助手发现 API 端点、运行安全扫描并查看项目中的漏洞。

可以做什么
通过对话列出项目并管理其安全设置。通过爬取或上传 OpenAPI/Swagger 定义发现 API 端点,并查看发现状态与历史。列出、新增和编辑入口点,包括 HTTP 方法、URL、请求头和请求体。启动安全扫描、查询扫描状态、查看扫描历史并列出可用测试(如 SQL 注入、XSS)。按严重程度、状态或入口点筛选查询漏洞。管理认证配置以及用于私有或本地目标的 repeater。
适用场景
当你希望 AI 编程助手在对话中驱动应用安全测试时使用:扫描公开或本地应用、从 API 规范发现端点,或在 Bright 项目中筛查严重和高危漏洞。
运行要求
远程 SSE/HTTP 端点 app.brightsec.com(或组织专用 Bright 集群主机名)。需要 Bright 账户和 API 密钥,通过 Authorization 头以 Api-Key 形式发送;密钥可为个人、项目或组织级别并具备相应权限范围。扫描私有或本地目标还需用 Bright CLI 运行 repeater。
安装前请注意
API 密钥是凭据,通过 Authorization 头发送;请使用限定范围的密钥,避免写入共享配置文件。扫描会向目标应用发送流量并消耗 Bright 平台资源。相关工具可创建和修改入口点、认证配置和 repeater,并启动扫描。Repeater 会让 Bright 云端的扫描流量经过你的本地网络,仅应为预期目标创建。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Bright Security,将其添加到工作区。
  2. 连接 Authorization token 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 SSE。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.NeuraLegion%2Fmcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "bright-security": {
      "type": "sse",
      "url": "https://app.brightsec.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Bright MCP Integration

Bright's Model Context Protocol (MCP) integration brings AI-powered application security testing directly into your development workflow. Your AI coding assistant can discover API endpoints, run security scans, and review vulnerabilities — all through natural language conversation.

Bright MCP is a remote, cloud-hosted MCP server. There is nothing to install locally — you simply point your MCP-compatible client at Bright's endpoint and authenticate with an API key.

Quick Start

1. Get a Bright API Key

Create a dedicated API key in your Bright account. This can be a personal, project, or organization-level key with the relevant scopes. See Personal API Key Scopes for details.

2. Configure Your Client

Add Bright as a remote MCP server in your IDE or tool of choice. The server URL is:

https://app.brightsec.com/mcp

Note: If your organization uses a dedicated Bright cluster, replace app.brightsec.com with your cluster's hostname.

See Client Configuration below for IDE-specific instructions.

3. Start Using It

Ask your AI assistant something like:

Scan https://my-app.example.com for security vulnerabilities

Your assistant will use the Bright MCP tools to list projects, discover entrypoints, run scans, and report findings.


Client Configuration

VS Code (GitHub Copilot)

Add the following to your MCP configuration (via Command Palette → "MCP: Add Server" → Global, or manually edit your mcp.json):

json
{  "servers": {    "brightsec.com": {      "type": "sse",      "url": "https://app.brightsec.com/mcp",      "headers": {        "Authorization": "Api-Key ${input:apiKey}"      }    }  },  "inputs": [    {      "type": "promptString",      "id": "apiKey",      "description": "Enter your Bright API Key",      "password": true    }  ]}

Then go to the Extensions tab, right-click the brightsec.com MCP server, and choose Start Server. You'll be prompted to enter your API key.

Full guide: Configure Bright MCP in VS Code

Augment Code

  1. Open the Augment Code extension settings → Tools → MCP.
  2. Click + Add remote MCP.
  3. Fill in:
    • Connection Type: HTTP
    • Authentication Type: Header
    • Name: BrightSec
    • URL: https://app.brightsec.com/mcp
    • Header Name: Authorization
    • Header Value: Api-Key YOUR_API_KEY
  4. Click Save.

Full guide: Configure Bright MCP in Augment Code

Cursor

Add to your Cursor MCP settings (.cursor/mcp.json):

json
{  "mcpServers": {    "brightsec": {      "url": "https://app.brightsec.com/mcp",      "headers": {        "Authorization": "Api-Key YOUR_API_KEY"      }    }  }}

Windsurf

Add to your Windsurf MCP configuration (~/.codeium/windsurf/mcp_config.json):

json
{  "mcpServers": {    "brightsec": {      "serverUrl": "https://app.brightsec.com/mcp",      "headers": {        "Authorization": "Api-Key YOUR_API_KEY"      }    }  }}

Generic MCP Client

Any MCP-compatible client that supports remote HTTP/SSE servers can connect to Bright. Configure it with:

SettingValue
TransportSSE (Server-Sent Events) or HTTP
URLhttps://app.brightsec.com/mcp
Auth HeaderAuthorization: Api-Key YOUR_KEY

Available Tools

Bright MCP exposes the following tools to your AI assistant:

Project Management

ToolDescription
listProjectsList all projects accessible to your API key. Use this to find project IDs needed for other operations.

Endpoint Discovery

ToolDescription
runDiscoveryDiscover API endpoints using crawling (crawlerUrls) or API definitions (fileId from uploadApiDefinition). Before running, check if the project already has entrypoints with listEntrypoints. For private/local targets, specify a connected repeater via repeaters.
getDiscoveryStatusGet the current status of a discovery run.
listDiscoveriesList discovery history for a project. View past discovery runs or monitor ongoing endpoint discovery.
uploadApiDefinitionUpload an API definition file (OpenAPI/Swagger) by URL or content. Returns a file ID to reference in discovery runs.

Entrypoint Management

ToolDescription
listEntrypointsList discovered API endpoints/URLs for a project. Use this to select entrypoints for scans or evaluate attack surface coverage. Supports filtering by HTTP method, status, and text search.
getEntrypointGet detailed information about a specific entrypoint by ID, including headers, body, and configuration.
addEntrypointAdd a new entrypoint to a project. Entrypoints define HTTP requests (method, URL, headers, body) that can be used for security scanning.
editEntrypointUpdate an existing entrypoint. Modify the HTTP request definition, authentication, or repeater settings.

Security Scanning

ToolDescription
runScanStart a security scan against selected entrypoints. Supports targeting specific entrypoints by ID or by status (e.g., new, changed, vulnerable). Configure which tests to run or use a scan template. For private/local targets, specify a connected repeater.
getScanStatusGet the current status of a running scan.
listScansList scan history for a project. View past scan results or check the status of multiple ongoing scans.
listTestsList all available security tests (e.g., SQL injection, XSS, CSRF) that can be included in scans.

Vulnerability Management

ToolDescription
listIssuesList security vulnerabilities found for a project. Filter by severity (Low, Medium, High, Critical), status (new, recurring, resolved, ignored), or entrypoint.

Authentication Configuration

ToolDescription
listAuthsList authentication configurations for a project. Use before scanning protected endpoints that require authentication.
getAuthGet detailed information about a specific authentication configuration.
addAuthCreate a new authentication configuration. Supports multiple auth types: static headers, OAuth 2.0/OIDC, multi-step HTTP flows, NTLM, browser-based login, and recorded browser flows.
editAuthUpdate an existing authentication configuration.

Private/Local Target Access

ToolDescription
createRepeaterCreate a repeater for accessing private/local targets. After creation, run the Bright CLI to start the repeater and establish the connection.
listRepeatersList repeaters and their connection status. Verify a repeater is connected before scanning non-public applications.

Usage Examples

Scan a Public Application

"Scan https://my-app.example.com for security vulnerabilities"

The assistant will:

  1. List your projects to find the appropriate one
  2. Get all discovered entrypoints for the project
  3. Run a security scan against those entrypoints
  4. Monitor the scan status and report findings

Discover Endpoints from an OpenAPI Spec

"Discover API endpoints from the OpenAPI spec at https://my-app.example.com/openapi.json"

The assistant will:

  1. Upload the OpenAPI definition file
  2. Run file-based discovery
  3. Monitor the discovery status

Scan a Local/Private Application

"Scan my local application at http://localhost:3000"

The assistant will:

  1. Check if Bright CLI is installed for repeater connectivity
  2. List your projects to find the appropriate one
  3. Create a repeater if needed
  4. Run a security scan through the repeater
  5. Monitor the scan status and report findings

Check for Critical Vulnerabilities

"Show me all critical and high severity issues in my project"

The assistant will:

  1. List your projects
  2. Query issues filtered by Critical and High severity
  3. Present findings with details

Scan with Authentication

"Scan my API that requires Bearer token authentication"

The assistant will:

  1. Create or find an existing auth configuration
  2. Set up the proper headers/token flow
  3. Run the scan with authentication applied

See the examples/ directory for more detailed workflow examples.


How It Works

┌─────────────────────┐         ┌──────────────────────┐│   AI Assistant       │  MCP    │   Bright Cloud       ││   (VS Code, Cursor,  │◄──────►│   (app.brightsec.com)││    Windsurf, etc.)   │  SSE    │                      │└─────────────────────┘         └──────────┬───────────┘                                           │                                           │ Scans                                           ▼                                ┌──────────────────────┐                                │   Your Application   │                                │   (public or via      │                                │    repeater)          │                                └──────────────────────┘
  1. Your AI assistant connects to Bright's MCP endpoint over SSE/HTTP.
  2. Bright's cloud platform receives tool calls and orchestrates security operations.
  3. Scans run against your application — either directly (public targets) or through a Repeater (private/local targets).

Repeaters (Private/Local Targets)

To scan applications that aren't publicly accessible, Bright uses Repeaters — lightweight agents that route scan traffic from Bright's cloud through your local network.

  1. Create a repeater via the MCP tool (createRepeater)
  2. Start the repeater using the Bright CLI:
    bash
    bright-cli repeater \  --id <REPEATER_ID> \  --hostname app.brightsec.com \  --token <YOUR_API_KEY>
  3. Reference the repeater when running scans or discoveries

See the Bright CLI Installation Guide for setup instructions.


Resources


License

This repository contains configuration examples and documentation for Bright's MCP integration. Bright's security scanning platform is a commercial SaaS product — visit brightsec.com for more information.

来源:README.md,提交 df1c3e3

工具

0
该服务器需要 API 密钥等凭据,因此 SourceWeft 无法在没有凭据的情况下读取其工具,也未收录。

版本历史

1
  1. v1.0.1最新Sep 16, 2026

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。