JADX MCP Server

MCP server for JADX-AI Plugin

MCP Servers Python Listed Apache-2.0

Is JADX MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.3 / 10
Provenance None
Signed commits 44%
Last push 3d ago
Compare JADX MCP Server
Suggest a correction

In detail: JADX MCP Server scores 50.6/100 (Grade C), ranked #924 of 1325 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 3.3/10; 44% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How JADX MCP Server compares in MCP Servers

  1. #525 MCP Virustotal 50.6 ±0
  2. #526 Ros2 MCP 50.6 ±0
  3. #527 JADX MCP Server 50.6 this agent
  4. #528 Help Scout MCP Server 50.5 −0.1
  5. #529 Nouz 50.4 −0.2

Bars show each HVTrust score; the tick marks JADX MCP Server’s 50.6.

Where the 50.6 comes from

HVTrust dimensions vs the MCP Servers average

50.6 / 100 · 100.0% confidence

JADX MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.3 / 25
4.0 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.3 / 17
0.9 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
13.2 / 20
1.2 above avg 12.0
AdoptionLog-scaled stars · package downloads
7.0 / 20
in line with avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-25
Rank Moved
Rank dropped 12 spots (#914 → #926)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.3/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.
60.5
Activity sub-score · out of 100
#527

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 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-09-26 12:32 UTC · Repo last pushed 3 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
795
Forks
130
Last Push
2026-09-23
3 days ago
Commits (4 wk)
4?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▲2
was #926

Analysis

Activity Inputs

60.5 / 100
StarsRepository reach
17.4 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
9.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.3 / 10
OpenSSF Scorecard · scanned Sep 24, 2026
Signed Commits
44%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 1
Contributors 0
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies -1
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 0

Common questions about JADX MCP Server

Public trust evidence for JADX MCP Server 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 JADX MCP Server publish package provenance?
No published build provenance is currently detected for JADX MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does JADX MCP Server have an OpenSSF Scorecard?
JADX MCP Server has an OpenSSF Scorecard score of 3.3/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 JADX MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does JADX MCP Server use?
JADX MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are JADX MCP Server's commits signed?
44% of the last 100 commits to JADX MCP Server 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
JADX MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
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 JADX MCP Server'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-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain JADX MCP Server?

For maintainers

HVTrust scores JADX MCP Server 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 22Grade 5HVTrust 3Listed 2Score 2Scorecard 1Surface 1Delisted 1MCP 1
2026-09-25
Rank Moved
Rank dropped 12 spots (#914 → #926)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 352 spots (#558 → #910)
2026-09-23
HVTrust Changed
HVTrust up 14.4pts (36.4 → 50.8)
2026-09-23
Activity Score Changed
Activity score up 8pts (53 → 61)
2026-09-22
Newly Listed
First tracked at rank #558
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Grade Changed
Trust grade C → D
2026-09-17
Rank Moved
Rank dropped 20 spots (#917 → #937)
2026-09-11
Rank Moved
Rank dropped 11 spots (#897 → #908)
2026-09-09
Grade Changed
Trust grade D → C
2026-09-09
Rank Moved
Rank rose 10 spots (#909 → #899)
2026-09-08
Rank Moved
Rank dropped 12 spots (#897 → #909)
2026-09-07
Rank Moved
Rank dropped 42 spots (#855 → #897)
2026-09-06
Rank Moved
Rank dropped 15 spots (#840 → #855)
2026-09-05
Grade Changed
Trust grade C → D
2026-09-05
Rank Moved
Rank dropped 156 spots (#684 → #840)
2026-09-05
HVTrust Changed
HVTrust down 3.3pts (53.2 → 49.9)
2026-09-05
Activity Score Changed
Activity score down 7pts (64 → 57)
2026-09-04
Rank Moved
Rank dropped 29 spots (#655 → #684)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-09-03
Rank Moved
Rank rose 29 spots (#684 → #655)
2026-09-02
Rank Moved
Rank dropped 19 spots (#665 → #684)
2026-09-01
Rank Moved
Rank dropped 26 spots (#639 → #665)
2026-08-31
Grade Changed
Trust grade D → C
2026-08-30
Rank Moved
Rank dropped 17 spots (#625 → #642)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.0/10
2026-08-29
Rank Moved
Rank rose 475 spots (#1100 → #625)
2026-08-29
HVTrust Changed
HVTrust up 26.7pts (22.1 → 48.8)
2026-08-28
Rank Moved
Rank dropped 27 spots (#1073 → #1100)
2026-08-27
Rank Moved
Rank dropped 23 spots (#1050 → #1073)
2026-08-26
Rank Moved
Rank dropped 79 spots (#971 → #1050)
2026-08-24
Rank Moved
Rank dropped 10 spots (#953 → #963)
2026-08-19
Rank Moved
Rank dropped 13 spots (#953 → #966)
2026-08-17
Rank Moved
Rank rose 14 spots (#968 → #954)
2026-08-16
Rank Moved
Rank dropped 25 spots (#943 → #968)
2026-08-10
Newly Listed
First tracked at rank #932

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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