Bright Security

com.brightsecPublished by brightsec.comOfficial publisherv1.0.0Updated Oct 24, 2026

Enables AI agents to access Bright Security tools for app discovery and security testing.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Bright Security MCP server that lets an AI assistant reach Bright Security tools for application discovery and security testing.

What you can do
  • Access Bright Security application discovery capabilities.
  • Run security testing through Bright Security tools.
  • Work against a Bright Security instance over a remote HTTP endpoint.
  • No tool list is published, so the exact actions available are not documented here.
When to use it
Useful when you already use Bright Security and want an assistant to drive app discovery or security testing from a chat session instead of the web UI.
Requirements
A remote Bright Security instance endpoint at the provider's subdomain, plus a Bright Security API key sent as a bearer token in the Authorization header. Network access to that instance is required.
Before you install
The API key is a secret passed in the Authorization header; keep it out of shared logs and transcripts. Security testing can send traffic to target applications, so confirm scope before letting an assistant run scans. The published tool list is empty, so review what the server exposes after connecting.

Installation

In SourceWeft

  1. Open Bright Security in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

39% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.