Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
The AI X-ray for any file: what is it, what does it hide, what changed. Built on REA.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"binsight": {
"command": "npx",
"args": [
"-y",
"binsight",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add binsight -- npx -y binsight mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"binsight": {
"command": "npx",
"args": [
"-y",
"binsight",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"binsight": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"binsight",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Alessiolucini, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (6.6.0) reached the registry 20 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, NexusWindows
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Offline · cross-platform · with evidence. It never runs the file.
Built on REA (morluto/rea) · MIT
Most files are black boxes: an .exe you downloaded, a firmware dump, a driver, a game, an ECU calibration, an app update. BinSight opens the box — statically, on your own machine, without ever running the file — and answers the three questions that matter, in plain language and with the evidence to back them up.
You: What is this file? Is it hiding anything? And what changed vs the old version?
BinSight: PE/Windows x64, compiled with MSVC, UPX-packed (entropy 7.9), imports consistent with network + process injection, Authenticode signature present, and vs the previous build 3 regions changed — here are the offsets. All static, all offline, with evidence.
triage_file and inspect_executable read ELF, PE/Windows and Mach-O (and raw blobs) and tell you the type, architecture, entry point, imports/exports, sections, hashes, and a compiler/packer fingerprint — without starting Ghidra or IDA, on macOS, Windows or Linux.
detect_binary_toolchain, measure_binary_entropy, classify_import_capabilities, identify_crypto_constants, extract_binary_strings, inspect_code_signature and scan_embedded_content surface packing, high-entropy regions, imported capabilities (network, process, crypto…), IOC strings, embedded files, and whether a signature is real — reported as evidence and inference, never as a verdict.
compare_binaries diffs any two files byte-for-byte and explains the change — which regions moved, what was zeroed or maxed out, the before/after values. Works on app updates, drivers, firmware and ECU calibration dumps alike. compare_executables adds import/export/section/hardening deltas for executables.
| Tool | What it answers |
|---|---|
| `triage_file` | One call: type, hashes, structure, entropy, packing, capabilities, signature, strings, next steps |
| `generate_triage_report` | A shareable Markdown triage report |
| `compare_binaries` | Diff any two files and explain what changed (firmware, ECU dumps, updates) |
| `compare_executables` | Diff two executables: imports, exports, sections, hardening, entropy |
| `inspect_executable` | Sections, imports, exports, libraries, symbols, entry point, overlay — ELF/PE/Mach-O |
| `inspect_binary_hardening` | checksec for every OS: PIE, canary, NX, RELRO, CFG, ASLR, hardened runtime |
| `measure_binary_entropy` | File / section / block Shannon entropy + chi-square |
| `detect_binary_toolchain` | Compiler, packer, installer, language (UPX, MSVC, PyInstaller, Go…) |
| `extract_binary_strings` | ASCII/UTF-16 strings classified into IOCs (URL, IP, path, registry…) |
| `identify_crypto_constants` | AES S-box, SHA/MD5, CRC32, ChaCha, curve parameters… |
| `classify_import_capabilities` | Capabilities inferred from imports ("consistent with", never a verdict) |
| `scan_byte_patterns` | Byte / hex-wildcard / text / regex search, no provider needed |
| `compute_similarity_hashes` | imphash, Rich hash, symhash, telfhash, ssdeep, TLSH |
| `inspect_code_signature` | Authenticode + Mach-O code signature — on any host |
| `scan_embedded_content` | binwalk-style embedded-file identification (offsets only) |
| `generate_sbom` | CycloneDX / SPDX component inventory from embedded metadata |
| `recover_go_symbols` | Function names from a stripped Go pclntab |
Every result separates observations, inferences and unknowns, carries file offsets, and states its limitations. Detection only — nothing is unpacked, decrypted, cracked or executed.
npx binsight triage-file /path/to/file --json
npx binsight compare-binaries /path/to/old /path/to/new --json npx binsight generate-triage-report /path/to/file --json
Register BinSight as an MCP server for your AI agent, then just ask it in plain language ("what is this file, what does it hide, what changed?"):
npx binsight setup
BinSight supports the same agents as REA — see supported agents; other clients can use manual MCP registration.
BinSight's parsers and hashes are checked against the tools analysts already trust: imphash matches `pefile` byte-for-byte, structure matches LIEF / readelf / otool, and hardening and packing results match checksec and Detect It Easy on a real corpus of ELF, PE and Mach-O binaries.
BinSight builds on REA and adds the static intelligence suite above. REA is MIT-licensed; this project keeps that license and attribution. This is not an official REA release — for REA itself, go to morluto/rea.
MIT. See LICENSE. Portions © the REA authors.