Flare vs Privacyscrubber MCP
A side-by-side look at the Flare and Privacyscrubber MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
FlareSecurity · Remote HTTP/SSEScan a running app or repo for leaked secrets, exposed routes and open RLS, and verify live keys37FairAuth: not declaredVerdict: choose Flare for security work over a hosted endpoint; choose Privacyscrubber MCP for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
FChoose Flare when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
Choose Privacyscrubber MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
audit_context, sanitize_text, scrub_text.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | F Flare | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 37/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 23 |
| Full listing | View Flare | View Privacyscrubber MCP |
Tools & capabilities
Flare tools
No tool names declared yet. Check the project README from the listing page.
Privacyscrubber MCP tools 23
audit_contextSTEP 0 (Pre-Flight): Non-destructive security inspection of raw prompts or document chunks before sending to LLMs. Evaluates PII, secrets, risk severity (CLEAN, LOW, MODERATE, CRITICAL), and triggered regulatory frameworks (GDPR, HIPAA, SOC 2, PCI DSS) with zero text mutation.sanitize_textSTEP 1: Call this first. You MUST NOT process raw user data before calling this. Locally scrubs PII, secrets, and credentials (like API keys, passwords, emails, phones, names) from code, logs, or text. Replaces them with safe placeholders (e.g., [EMAIL_1], [API_KEY_1]). Keep your data secure before passing it to any LLM. (For in-code backend services or RAG vector pipelines outside of MCP, use '@privacyscrubber/sdk': npm i @privacyscrubber/sdk)scrub_textAlias for 'sanitize_text'. Locally scrubs PII and secrets before LLM ingestion.reveal_textSTEP 3: Call this last. You MUST pass your final generated response through this tool to restore tokens (e.g., [EMAIL_1]) back with the original private data from the local volatile RAM-only session map before showing it to the user.sanitize_fileReads a local file, sanitizes its contents using the selected profile, and outputs the safe version for AI analysis. Securely keeps original identifiers in memory.scrub_fileAlias for 'sanitize_file'. Reads and sanitizes a local file.audit_directory_for_piiScans a local directory for leaks of secrets, keys, and PII. Returns a summary report. Use this tool for Security Auditing.redact_fileAction/Redact: In-place redaction of a local file. Replaces PII and secrets with tokens and saves the file. By default, creates a .bak backup. Use dry_run=true to test without modifying.create_default_configCreates a default 'privacyscrubber.json' configuration file in the active workspace root directory if one does not exist. Includes template structures for custom regex rules and exclusion bypass patterns.generate_compliance_reportGenerates an official Zero-Trust Compliance Audit Certificate (GDPR, HIPAA, EU AI Act, SOC 2) for the current MCP session. Returns cryptographic session hash, masked entities breakdown, and compliance certification.mark_false_positiveMarks a previously detected token as a false positive. The original plaintext value will be excluded from all future sanitize_text calls in this session. Returns the restored original value and updated ignore list size.check_statusReturns the current PrivacyScrubber MCP tier, session usage, available profiles, and PRO upgrade instructions. Call this to see your license status or get setup help.- +11 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Flare
{
"mcpServers": {
"flare": {
"url": "https://flarehq.dev/mcp"
}
}
}
Privacyscrubber MCP
{
"mcpServers": {
"moxno-privacyscrubber-mcp": {
"command": "npx",
"args": [
"-y",
"@privacyscrubber/mcp-server"
]
}
}
}
Frequently asked questions
Flare is categorized under Security and uses a remote HTTP/SSE transport. Privacyscrubber MCP belongs to Security and uses a local stdio subprocess. Pick Flare for security work and Privacyscrubber MCP for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Flare has no declared pricing — check the project's own site. Privacyscrubber MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add flare and moxno-privacyscrubber-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Flare has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Privacyscrubber MCP has 65/100 (Great) with 4 views, 0 installs and 2 GitHub stars.