A side-by-side look at the 4da MCP Server and Binary Ninja MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose 4da MCP Server for security work as a local process; choose Binary Ninja MCP for security as a local process. You can also run both side by side in one mcpServers block.
list_methods, get_entry_points, search_functions_by_name.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 45/100 · Fair | 71/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 | 2 | 450 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 1 installs 0 upvotes |
| Tools | Not listed | 54 |
| Full listing | View 4da MCP Server | View Binary Ninja MCP |
No tool names declared yet. Check the project README from the listing page.
list_methodsList all function names in the program with pagination.get_entry_pointsList entry point(s) of the loaded binary.search_functions_by_nameSearch for functions whose name contains the given substring.decompile_functionDecompile a specific function by name and return the decompiled C code.get_ilGet IL for a function in the selected view (hlil, mlil, llil).fetch_disassemblyRetrieve the disassembled code of a function as assembly mnemonic instructions.rename_functionRename a function by its current name. The configured prefix will be automatically prepended if not present.rename_single_variableRename a variable in a function.rename_multi_variablesRename multiple local variables in one call.rename_dataRename a data label at the specified address.set_commentSet a comment at a specific address.get_commentGet the comment at a specific address.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.
{
"mcpServers": {
"4da-mcp-server": {
"command": "npx",
"args": [
"-y",
"@4da/mcp-server"
]
}
}
}
{
"mcpServers": {
"fosdickio-binary-ninja-mcp": {
"command": "npx",
"args": [
"-y",
"binary-ninja-mcp"
]
}
}
}
