{"id":"invoke-re-binja-lattice-mcp","name":"binja-lattice-mcp","af_score":53.0,"security_score":43.8,"reliability_score":30.0,"what_it_does":"Provides a Binary Ninja plugin and MCP server bridge that lets clients query binary analysis data (functions, disassembly/pseudocode, types, tags, progress, strings/bytes/search) and also modify the active Binary Ninja database (rename functions/variables, add comments, set types/signatures, create structs/tags) over an HTTP/REST interface exposed to an MCP server/client workflow.","best_when":"Running locally (or within a trusted network) with short-lived credentials, where an agent can call MCP tools to read/annotate a single Binary Ninja database interactively.","avoid_when":"Exposing the service broadly to untrusted clients, logging/handling API keys insecurely, or when agent-driven write operations (renames/types/comments) require strict change governance.","last_evaluated":"2026-03-30T13:55:42.819089+00:00","has_mcp":true,"has_api":true,"auth_methods":["API key / token via environment variable (BNJLAT)","Username+password CLI client flags (password interpreted as API key/token)"],"has_free_tier":false,"known_gotchas":["Service prints/shows API key in Binary Ninja logs at server start—agents should avoid capturing/logging secrets.","Write tools can permanently alter the active Binary Ninja database; agents should confirm intended changes before applying.","Token expiration/renewal exists but retry/reauth behavior is not clearly documented for tool calls."],"error_quality":0.0}