Reversecore MCP vs Vulnicheck
A side-by-side look at the Reversecore MCP and Vulnicheck 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 Vulnicheck for security over a hosted endpoint. 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 Vulnicheck when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
check_package_vulnerabilities, scan_dependencies, scan_installed_packages.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 63/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 211 | 11 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 114 | 10 |
| Full listing | View Reversecore MCP | View Vulnicheck |
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
Vulnicheck tools 10
check_package_vulnerabilitiesCheck a specific Python package for vulnerabilitiesscan_dependenciesScan dependency files (requirements.txt, pyproject.toml, etc.)scan_installed_packagesScan currently installed Python packagesget_cve_detailsGet detailed information about a specific CVEscan_for_secretsDetect exposed secrets and credentials in codescan_dockerfileAnalyze Dockerfiles for vulnerable Python dependenciesscan_github_repoComprehensive security scan of GitHub repositoriesassess_operation_safetyAI-powered risk assessment for operationsvalidate_mcp_securityValidate MCP server security configurationscomprehensive_security_checkInteractive AI-powered security assessment
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"
]
}
}
}
Vulnicheck
{
"mcpServers": {
"vulnicheck": {
"url": "http://localhost:3000/mcp"
}
}
}
Frequently asked questions
Reversecore MCP is categorized under Security and uses a local stdio subprocess. Vulnicheck belongs to Security and uses a remote HTTP/SSE transport. Pick Reversecore MCP for security work and Vulnicheck 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. Vulnicheck has no declared pricing — check the project's own site. 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 vulnicheck 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. Vulnicheck has 49/100 (Fair) with 3 views, 0 installs and 11 GitHub stars.