# Flare [Health: Active]

**Category:** 🔒 Security  
**Repository:** https://flarehq.dev/mcp  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/flare

## Description
Scan a running app or repo for leaked secrets, exposed routes and open RLS, and verify live keys

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "flare": {
    "url": "https://flarehq.dev/mcp"
  }
}
```

## Documentation

## What Flare MCP server does

The Flare MCP server focuses on four security checks: finding leaked secrets, identifying exposed routes, detecting open RLS, and verifying live keys. Its stated inputs are a running app or a repository, so it can be considered when reviewing both deployed application behavior and code or configuration stored in a project.

These checks address different exposure types. Secret scanning looks for credentials or other sensitive values that may have been disclosed. Route checks focus on application endpoints that may be exposed. RLS checks look for database access policies that are too open. Live-key verification is intended to determine whether keys currently work rather than merely appearing in a codebase.

## How it works

You provide the Flare MCP server with a running application or repository to inspect. It then performs the supported security checks against that target: secret discovery, route exposure review, RLS review, and live-key verification. The available material does not describe authentication, result formats, scan depth, supported repository hosts, or how targets are supplied.

Because the description covers both running applications and repositories, the server may fit workflows that need to examine deployed behavior as well as project contents. The supplied information does not establish whether every check applies to both target types, so confirm the expected target and check combinations before adopting it for a specific pipeline.

## Tools and capabilities

The documented capabilities are:

- Scan a running app for leaked secrets.
- Scan a repository for leaked secrets.
- Check for exposed routes.
- Check for open RLS.
- Verify live keys.

The material does not provide individual MCP tool names, parameters, return values, or examples. Treat the capability list as the available scope rather than as a complete API reference.

## Limitations and notes

The Flare MCP server has limited published information in the supplied listing. There is no README content describing installation, configuration, environment variables, supported MCP clients, licensing, authentication, rate limits, or required permissions. Client compatibility therefore cannot be inferred from the listing alone.

The listing also does not explain what counts as a leaked secret, exposed route, or open RLS finding, nor does it state whether verification changes or revokes live keys. Use the server for the documented checks, but obtain implementation-specific guidance before relying on its results as the sole security control or integrating it into an automated remediation process.

_Full upstream README: https://allmcps.com/mcp/flare/readme_