updated 2026-10-13 04:10 UTC

IDA Pro MCP

Repository Website

AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.

MCP Servers Python Listed MIT

Is IDA Pro MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 2.7 / 10
Provenance None
Signed commits 47%
Last push 17d ago
Advisories None known
Compare IDA Pro MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: IDA Pro MCP scores 63.2/100 (Grade C), ranked #577 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.7/10; 47% of recent commits are signed; no published advisory affects its latest release (ida-pro-mcp); last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How IDA Pro 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships IDA Pro 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.

  1. Source Partly signed

    github.com/mrexodia/ida-pro-mcp, MIT, last pushed 2026-09-26. 47% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.7/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:

    • Code Review8
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow0
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 8
    Branch-Protection 0
    CI-Tests 3
    CII-Best-Practices 0
    Code-Review 8
    Contributors 10
    Dangerous-Workflow 0
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI ida-pro-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: ida-pro-mcp 1.4.0. No published advisory affects it (OSV, checked 2026-10-12).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of IDA Pro 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 IDA Pro 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.

Signed credential (JSON) How to verify

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 IDA Pro MCP compares in MCP Servers

  1. #319 Unity MCP 63.2 ±0
  2. #320 Cyberbro MCP Server 63.2 ±0
  3. #321 IDA Pro MCP 63.2 this agent
  4. #322 Outlook MCP 63.1 −0.1
  5. #323 MindsHub 62.9 −0.3

Bars show each HVTrust score; the tick marks IDA Pro MCP’s 63.2.

Where the 63.2 comes from

HVTrust dimensions vs the MCP Servers average

63.2 / 100 · 100.0% confidence

IDA Pro MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.7 / 25
4.7 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
10.8 / 17
1.4 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
16.1 / 20
3.9 above avg 12.2
AdoptionLog-scaled stars · package downloads
14.1 / 20
6.7 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 12 spots (#556 → #568)
2026-09-27
Rank Moved
Rank dropped 13 spots (#493 → #506)
2026-09-23
Rank Moved
Rank dropped 293 spots (#194 → #487)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.7/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for IDA Pro MCP View MCP Servers Report missing data
78.7
Activity sub-score · out of 100
#321
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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 →

Signals refreshed 2026-10-13 04:10 UTC · Repo last pushed 17 days ago

Rank Trend

2026-09-29 2026-10-13

Activity & Reach

Stars
12.7k
Forks
1.5k
Last Push
2026-09-26
17 days ago
Commits (4 wk)
20
Downloads (7d)
1,602
pypi
HN mentions (30d)
—
Open Issues
36
Rank Change
▼5
was #572

Analysis

Activity Inputs

78.7 / 100
StarsRepository reach
24.6 / 30
FreshnessLast push recency
22.6 / 25
ActivityRecent commits
16.5 / 25
CommunityFork signal
14.8 / 20

Common questions about IDA Pro MCP

IDA Pro MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does IDA Pro MCP publish package provenance?
No published build provenance is currently detected for IDA Pro MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does IDA Pro MCP have an OpenSSF Scorecard?
IDA Pro MCP has an OpenSSF Scorecard score of 2.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is IDA Pro MCP actively maintained?
Maintained. Last push was 17 days ago.
What license does IDA Pro MCP use?
IDA Pro MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are IDA Pro MCP's commits signed?
47% of the last 100 commits to IDA Pro MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
high confidence
Implemented
IDA Pro MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain IDA Pro MCP?

For maintainers

HVTrust scores IDA Pro 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 28HVTrust 1Grade 1
2026-10-09
Rank Moved
Rank dropped 12 spots (#556 → #568)
2026-09-27
Rank Moved
Rank dropped 13 spots (#493 → #506)
2026-09-23
Rank Moved
Rank dropped 293 spots (#194 → #487)
2026-09-21
Rank Moved
Rank rose 383 spots (#578 → #195)
2026-09-20
Rank Moved
Rank rose 27 spots (#605 → #578)
2026-09-17
Rank Moved
Rank dropped 67 spots (#537 → #604)
2026-09-16
Rank Moved
Rank rose 53 spots (#590 → #537)
2026-09-12
Rank Moved
Rank dropped 11 spots (#566 → #577)
2026-09-11
Rank Moved
Rank dropped 12 spots (#554 → #566)
2026-09-08
Rank Moved
Rank dropped 23 spots (#523 → #546)
2026-09-07
Rank Moved
Rank dropped 35 spots (#488 → #523)
2026-09-06
Rank Moved
Rank rose 39 spots (#527 → #488)
2026-09-05
Rank Moved
Rank dropped 121 spots (#406 → #527)
2026-09-04
Rank Moved
Rank dropped 33 spots (#373 → #406)
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 607 spots (#980 → #373)
2026-09-03
HVTrust Changed
HVTrust up 23.3pts (39.7 → 63.0)
2026-09-02
Rank Moved
Rank dropped 46 spots (#934 → #980)
2026-09-01
Rank Moved
Rank dropped 40 spots (#894 → #934)
2026-08-31
Rank Moved
Rank dropped 28 spots (#866 → #894)
2026-08-30
Rank Moved
Rank dropped 39 spots (#827 → #866)
2026-08-29
Rank Moved
Rank dropped 46 spots (#781 → #827)
2026-08-28
Rank Moved
Rank dropped 24 spots (#757 → #781)
2026-08-27
Rank Moved
Rank dropped 10 spots (#747 → #757)
2026-08-26
Rank Moved
Rank dropped 102 spots (#645 → #747)
2026-08-17
Rank Moved
Rank rose 11 spots (#641 → #630)
2026-08-16
Rank Moved
Rank dropped 16 spots (#625 → #641)
2026-08-10
Rank Moved
Rank dropped 21 spots (#597 → #618)
2026-08-08
Rank Moved
Rank dropped 209 spots (#389 → #598)
2026-07-29
Rank Moved
Rank dropped 10 spots (#371 → #381)
GitHub → Website → PyPI: ida-pro-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/ida-pro-mcp.svg)](https://hvtracker.net/agents/ida-pro-mcp)
HTML:
<a href="https://hvtracker.net/agents/ida-pro-mcp"><img src="https://hvtracker.net/badge/ida-pro-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON