Hex-Rays IDA MCP
Official Hex-Rays IDA MCP Server.
Is Hex-Rays IDA MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Hex-Rays IDA MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Hex-Rays IDA MCP scores 68.6/100 (Grade B), ranked #409 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 15% of recent commits are signed; no published advisory affects its latest release (ida-mcp); last pushed 2026-10-28. Every point is earned from checkable signals — never paid placement. How scoring works →
How Hex-Rays IDA MCP could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +18.4 → 87.0 A · #22 of 779
- Sign every commit15% signed today +4.3 → 72.9 B · #180 of 779
Chain of custody
Scanners check what the code says. This traces who ships Hex-Rays IDA MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/HexRaysSA/ida-mcp, MIT, last pushed 2026-10-28. 15% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
Published packages Linked and attested
- PyPI ida-mcp Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: ida-mcp 20261028.0.3. No published advisory affects it (OSV, checked 2026-11-10).
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Hex-Rays IDA MCP.
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Hex-Rays IDA MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Hex-Rays IDA MCP compares in MCP Servers
- #240 Amazon Ads MCP 68.6 ±0
- #241 Federal Compass MCP 68.6 ±0
- #242 Hex-Rays IDA MCP 68.6 this agent
- #243 Terraform MCP Server 68.5 −0.1
- #244 Dav MCP 68.5 −0.1
Bars show each HVTrust score; the tick marks Hex-Rays IDA MCP’s 68.6.
Where the 68.6 comes from
HVTrust dimensions vs the MCP Servers average
68.6 / 100 · 100.0% confidenceHex-Rays IDA MCP MCP Servers average (779 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Activity & Reach
Analysis
Activity Inputs
67.1 / 100Common questions about Hex-Rays IDA MCP
Does Hex-Rays IDA MCP publish package provenance?
Does Hex-Rays IDA MCP have an OpenSSF Scorecard?
Is Hex-Rays IDA MCP actively maintained?
What license does Hex-Rays IDA MCP use?
Are Hex-Rays IDA MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Hex-Rays IDA MCP?
For maintainers
HVTrust scores Hex-Rays IDA MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/hex-rays-ida-mcp)
<a href="https://hvtracker.net/agents/hex-rays-ida-mcp"><img src="https://hvtracker.net/badge/hex-rays-ida-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON