WatchGuard MCP
WatchGuard Cloud Firebox, Endpoint Security, ThreatSync, NDR and AuthPoint APIs for every customer
Descripción del creador (original en inglés)
AI-powered application security testing — scan APIs, discover endpoints, and find vulnerabilities.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
AuthorizationLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.
Ejecuta esto en tu terminal
claude mcp add --transport sse neuralegion https://app.brightsec.com/mcp --header 'Authorization: Api-Key {BRIGHTSEC_API_KEY}'Completa los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"neuralegion": {
"url": "https://app.brightsec.com/mcp",
"headers": {
"Authorization": "Api-Key {BRIGHTSEC_API_KEY}"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"neuralegion": {
"type": "sse",
"url": "https://app.brightsec.com/mcp",
"headers": {
"Authorization": "Api-Key {BRIGHTSEC_API_KEY}"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Authorization secreto obligatorio HTTP headerEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub NeuraLegion, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Aún sin revisar; revisamos los endpoints por turnos
Aún sin revisar; revisamos los endpoints por turnos
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: Authorization
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
El repo de GitHub cambió por última vez –, y la última versión (1.0.1) llegó al registro hace 8 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: WatchGuard MCP, ipdata MCP by usefulapi, MaxMind minFraud MCP by usefulapi
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
WatchGuard Cloud Firebox, Endpoint Security, ThreatSync, NDR and AuthPoint APIs for every customer
Look up location, network, company and threat data for IP addresses and ASNs in ipdata.
MCP server for MaxMind minFraud — score transactions for fraud risk from your AI assistant.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.
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.
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.
See Client Configuration below for IDE-specific instructions.
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.
Add the following to your MCP configuration (via Command Palette → "MCP: Add Server" → Global, or manually edit your mcp.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
https://app.brightsec.com/mcpAuthorizationApi-Key YOUR_API_KEYFull guide: Configure Bright MCP in Augment Code
Add to your Cursor MCP settings (.cursor/mcp.json):
{
"mcpServers": { "brightsec": { "url": "https://app.brightsec.com/mcp", "headers": { "Authorization": "Api-Key YOUR_API_KEY" } } } }
Add to your Windsurf MCP configuration (~/.codeium/windsurf/mcp_config.json):
{
"mcpServers": { "brightsec": { "serverUrl": "https://app.brightsec.com/mcp", "headers": { "Authorization": "Api-Key YOUR_API_KEY" } } } }
Any MCP-compatible client that supports remote HTTP/SSE servers can connect to Bright. Configure it with:
| Setting | Value |
|---|---|
| Transport | SSE (Server-Sent Events) or HTTP |
| URL | https://app.brightsec.com/mcp |
| Auth Header | Authorization: Api-Key YOUR_KEY |
Bright MCP exposes the following tools to your AI assistant:
| Tool | Description |
|---|---|
| listProjects | List all projects accessible to your API key. Use this to find project IDs needed for other operations. |
| Tool | Description |
|---|---|
| runDiscovery | 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. |
| getDiscoveryStatus | Get the current status of a discovery run. |
| listDiscoveries | List discovery history for a project. View past discovery runs or monitor ongoing endpoint discovery. |
| uploadApiDefinition | Upload an API definition file (OpenAPI/Swagger) by URL or content. Returns a file ID to reference in discovery runs. |
| Tool | Description |
|---|---|
| listEntrypoints | 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. |
| getEntrypoint | Get detailed information about a specific entrypoint by ID, including headers, body, and configuration. |
| addEntrypoint | Add a new entrypoint to a project. Entrypoints define HTTP requests (method, URL, headers, body) that can be used for security scanning. |
| editEntrypoint | Update an existing entrypoint. Modify the HTTP request definition, authentication, or repeater settings. |
| Tool | Description |
|---|---|
| runScan | 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. |
| getScanStatus | Get the current status of a running scan. |
| listScans | List scan history for a project. View past scan results or check the status of multiple ongoing scans. |
| listTests | List all available security tests (e.g., SQL injection, XSS, CSRF) that can be included in scans. |
| Tool | Description |
|---|---|
| listIssues | List security vulnerabilities found for a project. Filter by severity (Low, Medium, High, Critical), status (new, recurring, resolved, ignored), or entrypoint. |
| Tool | Description |
|---|---|
| listAuths | List authentication configurations for a project. Use before scanning protected endpoints that require authentication. |
| getAuth | Get detailed information about a specific authentication configuration. |
| addAuth | 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. |
| editAuth | Update an existing authentication configuration. |
| Tool | Description |
|---|---|
| createRepeater | Create a repeater for accessing private/local targets. After creation, run the Bright CLI to start the repeater and establish the connection. |
| listRepeaters | List repeaters and their connection status. Verify a repeater is connected before scanning non-public applications. |
"Scan https://my-app.example.com for security vulnerabilities"
The assistant will:
"Discover API endpoints from the OpenAPI spec at https://my-app.example.com/openapi.json"
The assistant will:
"Scan my local application at http://localhost:3000"
The assistant will:
"Show me all critical and high severity issues in my project"
The assistant will:
Critical and High severity"Scan my API that requires Bearer token authentication"
The assistant will:
See the examples/ directory for more detailed workflow examples.
┌─────────────────────┐ ┌──────────────────────┐
│ AI Assistant │ MCP │ Bright Cloud │ │ (VS Code, Cursor, │◄──────►│ (app.brightsec.com)│ │ Windsurf, etc.) │ SSE │ │ └─────────────────────┘ └──────────┬───────────┘ │ │ Scans ▼ ┌──────────────────────┐ │ Your Application │ │ (public or via │ │ repeater) │ └──────────────────────┘
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.
createRepeater) bright-cli repeater \
--id \ --hostname app.brightsec.com \ --token
3. Reference the repeater when running scans or discoveries
See the Bright CLI Installation Guide for setup instructions.
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.