Developer · Remote MCP server
Bright Security
AI-powered application security testing - scan APIs, discover endpoints, and find vulnerabilities.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.NeuraLegion/mcp- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- SSE (HTTP + Server-Sent Events)
- Published
- 2026-03-12
- Updated
- 2026-03-12
- Publisher
- NeuraLegion (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/NeuraLegion) · how
- Website
- docs.brightsec.com
- Repository
- github.com/NeuraLegion/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| SSE (HTTP + Server-Sent Events) | https://app.brightsec.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Bright Security
Bright Security is a remote MCP server reached over the older SSE transport, at https://app.brightsec.com/mcp. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| BridgisticConnect Claude to WordPress safely: signed requests, scoped keys, approvals, logs, snapshots. | Local · stdio |
| briefdGit-backed team knowledge compiled into token-budgeted context bundles for coding agents. | Local · HTTP |
| BriefPort Agent DeliveryCoding agents read frozen requirements, report progress, and submit delivery evidence. | Remote · HTTPLive check: sign-in required |
| briefroom MCPBriefroom stdio MCP server - expose the briefroom CLI to Claude Code, Codex, and other agents. | Local · stdio |
| brilliant.designLocal MCP bridge: your coding agent designs on Brilliant's real vector canvas, fully on 127.0.0.1. | Local · stdio |
| Bring Your AINo-data MCP handoff for local Claude Code to Codex harness moves. $49 lifetime. | Remote · HTTPLive check: ✓ handshake |
| brokreAI-safe credential broker for MCP - run saved SSH/MySQL/psql aliases; passwords never reach AI. | Local · stdio |
| BrowsegrabToken-efficient browser agent for local LLMs. Playwright + accessibility tree + MarkGrab. | Local · stdio |