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 分

    請在儲存庫或註冊中心條目中宣告授權條款。