Reversecore MCP vs Privacyscrubber MCP
A side-by-side look at the Reversecore MCP and Privacyscrubber MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Reversecore MCP for security work as a local process; 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?
Choose Reversecore MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You want tools like
audit_source_code, run_file, copy_to_workspace.
Choose Privacyscrubber MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
audit_context, sanitize_text, scrub_text.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 63/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 211 | 2 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 114 | 23 |
| Full listing | View Reversecore MCP | View Privacyscrubber MCP |
Tools & capabilities
Reversecore MCP tools 114
audit_source_codePerform a security audit on a source code file (SAST). This tool analyzes source code (C, C++, Python, Go, etc.) to identify potential security vulnerabilities such as buffer overflows, injection flaws, and weak cryptography. It provides a structured breakdown of dangerous patterns found in the code to guide deeper manual or AI-driven analysis. Use this tool when you have access to original source code or when you want to analyze decompiled output exported to a file.run_fileIdentify file metadata using the ``file`` CLI utility.copy_to_workspaceCopy any accessible file to the workspace directory. This tool allows copying files from any location (including AI agent upload directories) to the workspace where other reverse engineering tools can access them. Supports files from: - Claude Desktop uploads (/mnt/user-data/uploads) - Cursor uploads - Windsurf uploads - Local file paths - Any other accessible locationcreate_directoryCreate a new sub-directory within the workspace. This tool allows AI agents to dynamically create isolated sub-workspaces for different tasks or sessions.list_workspaceList all files in the workspace directory. Returns: ToolResult with list of files in workspacescan_workspaceBatch scan all files in the workspace using multiple tools in parallel. This tool performs a comprehensive scan of the workspace to identify files, analyze binaries, and detect threats. It runs 'run_file', 'parse_binary_with_lief', and 'run_yara' (if rules exist) on all matching files concurrently. **Workflow:** 1. Identify files matching patterns (default: all files) 2. Run 'file' command on all files 3. Run 'LIEF' analysis on executable files 4. Run 'YARA' scan if rules are available 5. Aggregate results into a single reportexplain_patchAnalyze differences between two binaries and explain changes in natural language. This tool combines binary diffing with decompilation to help understand security patches. It identifies changed functions, decompiles them, and uses heuristics to explain the nature of the changes (e.g., "Added bounds check", "Replaced unsafe API").assemble_instructionsAssemble assembly instruction strings into raw machine byte values using Keystone.create_memory_sessionCreate a new memory session to store memories. Use this when starting a new reverse engineering analysis. The session name should be descriptive and follow a template format like 'malware_analysis_2024_001' or 'game_cheat_detection'.save_memory_itemSave important information to long-term memory. Use this to remember: - Function addresses and their purposes - Vulnerability patterns discovered - API call sequences - User instructions and preferences - Interesting strings or structuresrecall_memory_itemSearch and recall memories from past analyses. Use this when you need to remember something from earlier, or when the user asks about previous findings.list_memory_sessionsList all analysis sessions with timestamps and status. Use this to see what analyses have been done before, or to find a session to resume.- +102 more on 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.
Reversecore MCP
{
"mcpServers": {
"reversecore-mcp": {
"command": "uvx",
"args": [
"reversecore-mcp"
]
}
}
}
Privacyscrubber MCP
{
"mcpServers": {
"moxno-privacyscrubber-mcp": {
"command": "npx",
"args": [
"-y",
"@privacyscrubber/mcp-server"
]
}
}
}
Frequently asked questions
Reversecore MCP is categorized under Security and uses a local stdio subprocess. Privacyscrubber MCP belongs to Security and uses a local stdio subprocess. Pick Reversecore MCP 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.
Reversecore MCP has no declared pricing — check the project's own site. Privacyscrubber MCP is listed as free. Auth: no auth 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 reversecore-mcp and moxno-privacyscrubber-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Reversecore MCP has a quality signal of 63/100 (Good) with 2 views, 0 installs and 211 GitHub stars. Privacyscrubber MCP has 65/100 (Great) with 5 views, 0 installs and 2 GitHub stars.