
Bright Security
Connects your AI coding assistant directly to Bright's application security platform to run vulnerability scans without leaving your editor. You get tools to discover API endpoints from URLs or OpenAPI specs, launch security tests for SQL injection, XSS, and other vulnerabilities, then review findings by severity. It handles authentication configs, manages scan history across projects, and supports scanning local apps through repeaters. Runs as a remote SSE server at app.brightsec.com/mcp, so there's nothing to install locally. You just authenticate with a Bright API key and ask your assistant to scan a URL. Good fit if you're already using Bright and want security testing in your AI workflow instead of switching to their web dashboard.
- tools
- 20
- auth
- Secret needed
- transport
- SSE
- last updated
- Mar 12, 2026
Tools
20 toolsPublic tool metadata for what this MCP can expose to an agent.
listProjectsList all projects accessible to your API key. Use this to find project IDs needed for other operations.
List all projects accessible to your API key. Use this to find project IDs needed for other operations.
No parameter schema in public metadata yet.
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`.
Discover 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`.
No parameter schema in public metadata yet.
getDiscoveryStatusGet the current status of a discovery run.
Get the current status of a discovery run.
No parameter schema in public metadata yet.
listDiscoveriesList discovery history for a project. View past discovery runs or monitor ongoing endpoint discovery.
List discovery history for a project. View past discovery runs or monitor ongoing endpoint discovery.
No parameter schema in public metadata yet.
uploadApiDefinitionUpload an API definition file (OpenAPI/Swagger) by URL or content. Returns a file ID to reference in discovery runs.
Upload an API definition file (OpenAPI/Swagger) by URL or content. Returns a file ID to reference in discovery runs.
No parameter schema in public metadata yet.
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.
List 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.
No parameter schema in public metadata yet.
getEntrypointGet detailed information about a specific entrypoint by ID, including headers, body, and configuration.
Get detailed information about a specific entrypoint by ID, including headers, body, and configuration.
No parameter schema in public metadata yet.
addEntrypointAdd a new entrypoint to a project. Entrypoints define HTTP requests (method, URL, headers, body) that can be used for security scanning.
Add a new entrypoint to a project. Entrypoints define HTTP requests (method, URL, headers, body) that can be used for security scanning.
No parameter schema in public metadata yet.
editEntrypointUpdate an existing entrypoint. Modify the HTTP request definition, authentication, or repeater settings.
Update an existing entrypoint. Modify the HTTP request definition, authentication, or repeater settings.
No parameter schema in public metadata yet.
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.
Start 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.
No parameter schema in public metadata yet.
getScanStatusGet the current status of a running scan.
Get the current status of a running scan.
No parameter schema in public metadata yet.
listScansList scan history for a project. View past scan results or check the status of multiple ongoing scans.
List scan history for a project. View past scan results or check the status of multiple ongoing scans.
No parameter schema in public metadata yet.
listTestsList all available security tests (e.g., SQL injection, XSS, CSRF) that can be included in scans.
List all available security tests (e.g., SQL injection, XSS, CSRF) that can be included in scans.
No parameter schema in public metadata yet.
listIssuesList security vulnerabilities found for a project. Filter by severity (`Low`, `Medium`, `High`, `Critical`), status (`new`, `recurring`, `resolved`, `ignored`), or entrypoint.
List security vulnerabilities found for a project. Filter by severity (`Low`, `Medium`, `High`, `Critical`), status (`new`, `recurring`, `resolved`, `ignored`), or entrypoint.
No parameter schema in public metadata yet.
listAuthsList authentication configurations for a project. Use before scanning protected endpoints that require authentication.
List authentication configurations for a project. Use before scanning protected endpoints that require authentication.
No parameter schema in public metadata yet.
getAuthGet detailed information about a specific authentication configuration.
Get detailed information about a specific authentication configuration.
No parameter schema in public metadata yet.
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.
Create 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.
No parameter schema in public metadata yet.
editAuthUpdate an existing authentication configuration.
Update an existing authentication configuration.
No parameter schema in public metadata yet.
createRepeaterCreate a repeater for accessing private/local targets. After creation, run the Bright CLI to start the repeater and establish the connection.
Create a repeater for accessing private/local targets. After creation, run the Bright CLI to start the repeater and establish the connection.
No parameter schema in public metadata yet.
listRepeatersList repeaters and their connection status. Verify a repeater is connected before scanning non-public applications.
List repeaters and their connection status. Verify a repeater is connected before scanning non-public applications.
No parameter schema in public metadata yet.
Sponsors
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.comwith your cluster's hostname.
Details
- Repository
- github.com/neuralegion/mcp
- Website
- docs.brightsec.com
- Category
- Security & Pentesting
- Transport
- SSE
- Auth
- Required
- Registry
- MCP registry, active