QNSQY
Linux only, local: post-quantum CBOM scan, encrypt to public keys, verify. Takes no secrets
Description from the maker (original English)
AI-powered application security testing — scan APIs, discover endpoints, and find vulnerabilities.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport sse neuralegion https://app.brightsec.com/mcp --header 'Authorization: Api-Key {BRIGHTSEC_API_KEY}'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"neuralegion": {
"url": "https://app.brightsec.com/mcp",
"headers": {
"Authorization": "Api-Key {BRIGHTSEC_API_KEY}"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"neuralegion": {
"type": "sse",
"url": "https://app.brightsec.com/mcp",
"headers": {
"Authorization": "Api-Key {BRIGHTSEC_API_KEY}"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account NeuraLegion, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 8 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: QNSQY, Gluo, Seal Security
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Linux only, local: post-quantum CBOM scan, encrypt to public keys, verify. Takes no secrets
Free agent tools, no sign-in: browser flows, test inboxes, web extract, site and security scans.
Vulnerability management: scan projects, search sealed packages, manage sealing rules and reports.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.