# Flare (npm · flarehq-mcp)

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

- Trust score: 76/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `flarehq-mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/dev-flarehq-security/flarehq-mcp.md), [page](https://verifymcp.io/servers/dev-flarehq-security/flarehq-mcp)

## Channel facts

- Registry: `npm`
- Package: `flarehq-mcp`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 37 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 770 tokens (~192/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Flare MCP server?

Flare runs locally as an npm package, launched with npx -y flarehq-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add dev-flarehq-security -- npx -y flarehq-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-flarehq-security": {
      "command": "npx",
      "args": [
        "-y",
        "flarehq-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-flarehq-security": {
      "command": "npx",
      "args": [
        "-y",
        "flarehq-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-flarehq-security -- npx -y flarehq-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-flarehq-security": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "flarehq-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-flarehq-security --command npx --arg -y --arg flarehq-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-flarehq-security:
    command: "npx"
    args: ["-y", "flarehq-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-flarehq-security": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "flarehq-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-flarehq-security -t stdio -c npx -a -y flarehq-mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-flarehq-security": {
      "command": "npx",
      "args": [
        "-y",
        "flarehq-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 76, −2)

- [functional] Stability: pass → 0.80

### 2026-09-18 (score 78, 0)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 76, −2)

- [functional] Stability: pass → 0.83

### 2026-09-11 (score 78, 0)

- [security] Stability: 0.97 → pass

### 2026-09-10 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `flare_scan_url` (~173 tokens)

Scan a running app for exposed secrets and misconfigurations

Runs Flare's full external security scan against a URL and returns ranked findings with fixes. Works against localhost (e.g. http://localhost:3000), so you can start the dev server and scan it before the code ever ships. Checks: secrets in bundles (each verified live against the issuing provider), secrets leaked through React Server Component props, NEXT_PUBLIC_ misuse, tokens in URLs, Supabase/Firebase table & storage exposure, unauthenticated and shadow API routes, unauthenticated LLM proxies, security headers, exposed .env/.git files, and SPF/DMARC. All checks are read-only.

Input parameters:

- `failOn` (string): Severity threshold for the BLOCKING verdict. Defaults to 'critical'.
- `url` (string, required): Full URL to scan, including scheme. Localhost is supported.

### `flare_scan_repo` (~106 tokens)

Scan a local repository for committed secrets and unsafe migrations

Runs Flare's deep source scan over a local directory: committed credentials, .env handling, unsafe SQL migrations (disabled RLS, allow-all policies), unprotected route handlers, and dependency issues. Findings include file and line so they can be fixed directly. Reads the filesystem only; nothing is uploaded.

Input parameters:

- `failOn` (string): Severity threshold for the BLOCKING verdict. Defaults to 'critical'.
- `path` (string): Directory to scan. Defaults to the current directory.

### `flare_verify_credential` (~166 tokens)

Check whether a credential is still live

Given a credential you have already found, checks whether it still authenticates by making a single read-only identity request to the provider that issued it (OpenAI, Anthropic, Stripe, GitHub, Slack, Google, or a Supabase service_role JWT). Non-billable and non-mutating: no model calls, no writes. Use this to tell a real incident from an already-rotated key before alarming the user. The credential is sent only to its own issuer.

Input parameters:

- `credential` (string, required): The raw credential value to check.
- `kind` (string): Credential type if known, e.g. 'OpenAI API key', 'Stripe live secret key', 'GitHub token', 'Supabase service_role key'. Inferred from the value when omitted.

### `flare_authz_test` (~325 tokens)

Test for broken object-level authorization (IDOR) across two accounts

Detects the top OWASP API risk — objects readable by accounts that do not own them (IDOR), and privileged routes reachable by non-privileged accounts. Give it URLs that return one account's objects plus the session headers for TWO different accounts, and it requests each URL as the other account and compares. A finding is reported ONLY when the second account receives the first account's exact data — an API that safely scopes the response to its own caller is correctly reported as safe. Reads only: it sends GET requests and never creates, changes or deletes anything. LOCALHOST ONLY for now (http://localhost:3000, 127.0.0.1) — testing a deployed origin needs an ownership-proof step that does not exist yet. Run this against your own dev server, ideally with two throwaway accounts in different tenants.

Input parameters:

- `adminUrls` (array): Optional privileged/admin routes to request as the 'other' account, to test function-level auth.
- `otherHeaders` (object, required): Auth headers for a DIFFERENT account, ideally in a different tenant/org so legitimate team sharing is not mistaken for IDOR.
- `ownerHeaders` (object, required): Auth headers for the owner account, e.g. { "Cookie": "session=..." } or { "Authorization": "Bearer ..." }.
- `ownerUrls` (array, required): URLs that return the OWNER account's objects, e.g. ['http://localhost:3000/api/invoices/123']. Use ids the owner account actually owns — the tool proves ownership by fetching these as the owner first.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-flarehq-security/flarehq-mcp#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 78
- 2026-09-17: 78
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 77
- 2026-09-13: 76
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 78
- 2026-09-09: 77
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 76
- 2026-09-05: 76
- 2026-09-04: 75
- 2026-09-03: 75
- 2026-09-02: 74
- 2026-09-01: 74
- 2026-08-31: 73
- 2026-08-30: 73
- 2026-08-29: 72
- 2026-08-28: 72
- 2026-08-27: 71
- 2026-08-26: 71
- 2026-08-25: 69
- 2026-08-24: 69
- 2026-08-23: 68
- 2026-08-22: 68

## Common questions

### What is the Flare MCP server?

Flare is an MCP server listed in the public MCP registry as dev.flarehq/security. Scan a running app or repo for leaked secrets, exposed routes and open RLS, and verify live keys. This page covers its npm package (flarehq-mcp).

### Is the Flare MCP server safe to use?

Flare scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Flare MCP server expose?

Flare exposes 4 tools: flare_scan_url, flare_scan_repo, flare_verify_credential, flare_authz_test. Their descriptions and schemas cost roughly 770 tokens of context every time the server is loaded.

### Is the Flare MCP server still maintained?

Flare is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Flare MCP server under?

Flare declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/flarehq-mcp
- Socket report: https://socket.dev/npm/package/flarehq-mcp
- Website: https://flarehq.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-flarehq-security/flarehq-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-flarehq-security/flarehq-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-flarehq-security/flarehq-mcp