IDA Pro MCP

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

MCP Servers Python Grade D Listed MIT
40.2/100
Rank #596 of 1204
Compare IDA Pro MCP

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-09 · 0d ago
Recent change
Rank +2

Is IDA Pro MCP safe? IDA Pro MCP scores 40.2/100 (Grade D), ranked #596 of 1204 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.8/10; 39% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-08
Rank Moved
Rank dropped 209 spots (#389 → #598)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared
2026-08-07
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.8/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.
82.0
Activity sub-score · out of 100
#242

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-09 20:01 UTC · Repo last pushed today

Activity & Reach

Stars
11.2k
Forks
1.3k
Last Push
2026-08-09
today
Commits (4 wk)
28?
Downloads (7d)
HN mentions (30d)
Open Issues
32
Rank Change
▲2
was #598

Analysis

HVTrust Dimensions vs MCP Servers

40.2 / 100 · 67.0% confidence

IDA Pro MCP MCP Servers average (718 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.5 / 25
in line with avg 5.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
10.9 / 17
2.1 above avg 8.8
Maintenance60% last-push freshness · 40% commit activity
14.9 / 20
2.4 above avg 12.5
AdoptionLog-scaled stars · package downloads
9.7 / 20
4.2 above avg 5.5

Activity Inputs

82.0 / 100
StarsRepository reach
24.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
18.2 / 25
CommunityFork signal
14.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.8 / 10
OpenSSF Scorecard · scanned Aug 9, 2026
Signed Commits
39%
of last 100 commits verified
Binary-Artifacts 8
Branch-Protection 0
CI-Tests 5
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

Is IDA Pro MCP safe?

Public trust evidence for IDA Pro MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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.8/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?
Actively maintained. The repository was pushed to within the last 1 day(s).
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?
39% 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
How this surface has changed

Detected changes to IDA Pro MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared
2026-08-07
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic

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.

Reputation Timeline

Signal history
Rank 3Listed 1HVTrust 1Scorecard 1Surface 1Surface 1
2026-08-08
Rank Moved
Rank dropped 209 spots (#389 → #598)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared
2026-08-07
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-07-29
Rank Moved
Rank dropped 10 spots (#371 → #381)
2026-07-15
Scorecard Added
OSSF Scorecard: 2.5/10
2026-07-15
Rank Moved
Rank rose 28 spots (#399 → #371)
2026-07-15
HVTrust Changed
HVTrust up 15.4pts (22.8 → 38.2)
2026-07-14
Newly Listed
First tracked at rank #399

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 40.2 Grade D
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.2 · Raw JSON