re-mcp (jtsylve/re-mcp) is an MCP server listed on the M8ven Trust Index. It scores 86 out of 100, grade B. It declares 326 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Caution
86/100
7 days ago

re-mcp

A multi-backend MCP server that exposes binary analysis capabilities from IDA Pro and Ghidra, allowing LLMs to directly drive reverse-engineering tools via natural language.

→ jtsylve/re-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

jtsylve

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configIDA_MCP_ALLOW_SCRIPTSSet to 1, true, or yes to enable the run_script tool for arbitrary IDAPython execution
configIDA_MCP_LOG_DIR
configIDA_MCP_LABEL
configIDA_MCP_LOG_LEVEL
configXDG_STATE_HOMELinux: $/<backend>/daemon.json (defaults to ~/.local/state/<backend>/daemon.json)
configRE_MCP_BACKEND
configIDA_MCP_MAX_WORKERS
configGHIDRA_INSTALL_DIR1. environment variable — checked first; set this if Ghidra is in a non-standard location.
configIDADIR1. environment variable — checked first; set this if IDA is in a non-standard location.
configIDAUSR
config_RE_MCP_DEPRECATED_CLI
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

327/327 tools missing one or more hints — reanalyze_range (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wait_for_analysis (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_analysis_problems (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +324 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — generate_exe_file deletes at line 370 (os.unlink(path))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool test coverage

Only 24/327 tools referenced in tests (7%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/jtsylve/re-mcp?variant=verified)](https://m8ven.ai/mcp/jtsylve/re-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 799239ff556f399ebfcf70259ac8db595eaa2610
code hash: 517575baba5a6f799a6f10bc07cd29b1abc576e198b7c50e83d6ad374d47dc17
verified: 9/4/2026, 12:09:27 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client