Developer · Local MCP server
Reversecore MCP
Security-first MCP server for reverse engineering, malware analysis, forensics, and SAST.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.sjkim1127/reversecore-mcp- Version
- 3.0.5
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI, OCI image (Docker)
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- sjkim1127 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/sjkim1127) · how
- Repository
- github.com/sjkim1127/Reversecore_MCP
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | reversecore-mcp | 3.0.5 | stdio |
| OCI image (Docker) | ghcr.io/sjkim1127/reversecore_mcp:3.0.5 | - | stdio |
How to connect Reversecore MCP
Reversecore MCP runs locally from a Python package published to PyPI: reversecore-mcp version 3.0.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx reversecore-mcp.
Reversecore MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/sjkim1127/reversecore_mcp:3.0.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm ghcr.io/sjkim1127/reversecore_mcp:3.0.5.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"reversecore-mcp": {
"command": "uvx",
"args": [
"reversecore-mcp"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| RetascThe issue tracker AI coding agents pull work from: atomic claims, dependency-aware dispatch. | Remote · HTTPLive check: ✓ handshake |
| Retell AIRetell AI MCP server: voice agent phone calls, agent management, LLMs, and voice discovery. | Local · stdio |
| retriEVALLLM evals as MCP tools: score outputs for faithfulness, relevancy, and hallucination. | Local · stdio |
| Reuse Before GenerateChecks whether your idea already exists before your agent builds it. Searches GitHub, npm, Python. | Local · stdio |
| Revibe MCPAnalyze any codebase - get architecture, file roles, execution flows, and agent context. | Local · stdio |
| Review MCPMulti-model code review: a panel of models + detectors return a pass/fail verdict. Paid via x402. | Remote · HTTPLive check: ✓ handshake |
| ReviewGateCode review against your team standards, before the pull request: generator finds, judge confirms. | Local · stdio |
| ReviewGuardSafety boundary for agent written GitHub PR reviews: pending and invisible, submitting is opt-in. | Local · stdio |