Skip to main content
Glama
u21h2

BinDiff MCP Tool

by u21h2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
IDADIRYesPath to the IDA Pro installation directory (containing idat and idalib). Required on Linux platforms.
MCP_TIMEOUTNoTimeout for analysis steps in seconds.3600
BINDIFF_PATHNoPath to the bindiff executable. If not provided, the tool attempts to auto-detect it from the system PATH.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
bindiff_compareA
Compares two binary files using IDA Pro and BinDiff.
Resulting detailed difference lists are saved to the specified directory (default: current directory).
Generated files:
1. matched_similar.json (Identical functions)
2. matched_different.json (Matched but Changed functions)
3. primary_only.json (Unmatched in Primary)
4. secondary_only.json (Unmatched in Secondary)

Args:
    primary_binary: Path to the first binary (e.g. original)
    secondary_binary: Path to the second binary (e.g. patched)
    output_results_dir: Directory to save the result files (default: current dir)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clearly defined purpose of comparing binary files using BinDiff and IDA Pro.

Naming Consistency5/5

The single tool name 'bindiff_compare' follows a clear verb_noun pattern and is consistent with itself. There are no other tools to create inconsistency.

Tool Count2/5

A single tool is generally too few for most server purposes, making the surface feel thin and incomplete. While this might be appropriate for a very narrow utility, it limits functionality and suggests the server may be under-scoped.

Completeness2/5

The server appears focused on binary comparison, but with only a compare tool, there are significant gaps. Missing operations might include analyzing results, managing comparisons, or integrating with other BinDiff features, making the surface incomplete for typical binary analysis workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources