Binary Ninja MCP Server
binary-ninja-mcp
npm
v1.0.0
Published by fosdickio — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Model Context Protocol server for Binary Ninja - enables seamless integration of Binary Ninja's capabilities with MCP clients
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 54
Each tool and what it can reach — statically extracted from the published source.
fetch_disassemblyingests untrusted inputconvert_numberno sensitive capabilitydeclare_c_typeno sensitive capabilitydecompile_functionno sensitive capabilitydefine_typesno sensitive capabilitydelete_commentno sensitive capabilitydelete_function_commentno sensitive capabilityformat_valueno sensitive capabilityfunction_atno sensitive capabilityget_binary_statusno sensitive capability
Show 44 more tools ↓
get_commentno sensitive capabilityget_data_declno sensitive capabilityget_entry_pointsno sensitive capabilityget_function_commentno sensitive capabilityget_ilno sensitive capabilityget_stack_frame_varsno sensitive capabilityget_type_infono sensitive capabilityget_user_defined_typeno sensitive capabilityget_xrefs_tono sensitive capabilityget_xrefs_to_enumno sensitive capabilityget_xrefs_to_fieldno sensitive capabilityget_xrefs_to_structno sensitive capabilityget_xrefs_to_typeno sensitive capabilityget_xrefs_to_unionno sensitive capabilityhexdump_addressno sensitive capabilityhexdump_datano sensitive capabilitylist_all_stringsno sensitive capabilitylist_binariesno sensitive capabilitylist_classesno sensitive capabilitylist_data_itemsno sensitive capabilitylist_exportsno sensitive capabilitylist_importsno sensitive capabilitylist_local_typesno sensitive capabilitylist_methodsno sensitive capabilitylist_namespacesno sensitive capabilitylist_platformsno sensitive capabilitylist_sectionsno sensitive capabilitylist_segmentsno sensitive capabilitylist_stringsno sensitive capabilitylist_strings_filterno sensitive capabilitymake_function_atno sensitive capabilitypatch_bytesno sensitive capabilityrename_datano sensitive capabilityrename_functionno sensitive capabilityrename_multi_variablesno sensitive capabilityrename_single_variableno sensitive capabilityretype_variableno sensitive capabilitysearch_functions_by_nameno sensitive capabilitysearch_typesno sensitive capabilityselect_binaryno sensitive capabilityset_commentno sensitive capabilityset_function_commentno sensitive capabilityset_function_prototypeno sensitive capabilityset_local_variable_typeno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (54 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
A 96/100 | 0 | 1.13.0 | 2026-09-08 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan binary-ninja-mcp --onlineMore in Other
A Model Context Protocol server implementation for AdGuard Home that enables AI agents to query and manage DNS records, filtering rules and more
Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.
MCP server with Airtable integration
A free one-minute reset for people, delivered by AI, with no account or personal data.
Access SEC filings efficiently, save time and tokens, and get cited answers.
A smart [MCP](https://modelcontextprotocol.io) server for [AniList](https://anilist.co) that gets your anime/manga taste - not just API calls.