GhidraMCP vs Safetyreplay MCP
A side-by-side look at the GhidraMCP and Safetyreplay MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GhidraMCP for security work over a hosted endpoint; choose Safetyreplay MCP 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 GhidraMCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Choose Safetyreplay MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
run_safety_replay, check_policy_gate, record_eval_receipt.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 60/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | No auth required | API key required |
| Pricing | Free | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11,518 | 0 |
| Directory activity | 12 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View GhidraMCP | View Safetyreplay MCP |
Tools & capabilities
GhidraMCP tools
No tool names declared yet. Check the project README from the listing page.
Safetyreplay MCP tools 5
run_safety_replaycheck_policy_gaterecord_eval_receiptsuggest_control_fixexport_release_evidence
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.
GhidraMCP
{
"mcpServers": {
"lauriewired-ghidramcp": {
"url": "http://127.0.0.1:8081/sse"
}
}
}
Safetyreplay MCP
{
"mcpServers": {
"safetyreplay-mcp": {
"url": "https://safetyreplay.clauxel.com/mcp"
}
}
}
Frequently asked questions
GhidraMCP is categorized under Security and uses a remote HTTP/SSE transport. Safetyreplay MCP belongs to Security and uses a remote HTTP/SSE transport. Pick GhidraMCP for security work and Safetyreplay 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.
GhidraMCP is listed as free. Auth: no auth required. Safetyreplay MCP is listed as a paid service. 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 lauriewired-ghidramcp and safetyreplay-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GhidraMCP has a quality signal of 60/100 (Good) with 12 views, 0 installs and 11,518 GitHub stars. Safetyreplay MCP has 49/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.