Decapodkernel MCP vs GhidraMCP
A side-by-side look at the Decapodkernel MCP and GhidraMCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Decapodkernel MCP for security work over a hosted endpoint; choose GhidraMCP 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 Decapodkernel MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
create_intent_contract, check_agent_boundary, record_completion_proof.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 48/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| 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 | 0 | 11,485 |
| Directory activity | 1 views 0 installs 0 upvotes | 12 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Decapodkernel MCP | View GhidraMCP |
Tools & capabilities
Decapodkernel MCP tools 4
create_intent_contractcheck_agent_boundaryrecord_completion_proofexport_intent_receipt
GhidraMCP tools
No tool names declared yet. Check the project README from 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.
Decapodkernel MCP
{
"mcpServers": {
"decapodkernel-mcp": {
"url": "https://decapodkernel.clauxel.com/mcp"
}
}
}
GhidraMCP
{
"mcpServers": {
"lauriewired-ghidramcp": {
"url": "http://127.0.0.1:8081/sse"
}
}
}
Frequently asked questions
Decapodkernel MCP is categorized under Security and uses a remote HTTP/SSE transport. GhidraMCP belongs to Security and uses a remote HTTP/SSE transport. Pick Decapodkernel MCP for security work and GhidraMCP 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.
Decapodkernel MCP has no declared pricing — check the project's own site. GhidraMCP 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 decapodkernel-mcp and lauriewired-ghidramcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Decapodkernel MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. GhidraMCP has 60/100 (Good) with 12 views, 0 installs and 11,485 GitHub stars.