Is Reversecore MCP safe to use?

Reversecore MCP has an HVTrust score of 77.8/100 (Grade B), ranked #120 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Reversecore MCP?

Reversecore MCP scores 77.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 198 GitHub stars and is categorized under MCP Servers.

Reversecore MCP

sjkim1127/Reversecore_MCP

A security-first MCP server that empowers AI agents to perform automated reverse engineering, malware analysis, forensic

MCP Servers Python Grade B Listed MIT

77.8/100

Rank #120 of 1320

Compare Reversecore MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-04 · 0d ago

Recent change

Rank +4

Is Reversecore MCP safe? Reversecore MCP scores 77.8/100 (Grade B), ranked #120 of 1320 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; OSSF Scorecard rates its supply-chain practices 5.7/10; 27% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#53 MCP Open Library — 78.3 (B) → #54 Opik MCP Server — 78.1 (B) → #56 Anytype MCP — 77.6 (B) → #57 MikroMCP — 77.6 (B) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-08-31

Rank Moved

Rank dropped 16 spots (#106 → #122)

2026-08-29

Scorecard Added

OSSF Scorecard: 5.7/10

2026-08-29

Grade Changed

Trust grade C → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.7/10. Tighten the weakest checks to improve public safety evidence.

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 Reversecore MCP View MCP Servers Report missing data

65.6

Activity sub-score · out of 100

#55

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 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 →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

198

Forks

Last Push

2026-09-04

today

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲5

was #125

Analysis

HVTrust Dimensions vs MCP Servers

77.8 / 100 · 100.0% confidence

Reversecore MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

16.0 / 25

6.4 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.5 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

18.6 / 20

6.4 above avg 12.2

AdoptionLog-scaled stars · package downloads

7.5 / 20

1.2 above avg 6.3

Activity Inputs

65.6 / 100

StarsRepository reach

13.8 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

20.7 / 25

CommunityFork signal

6.1 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

5.7 / 10

OpenSSF Scorecard · scanned Aug 29, 2026

Signed Commits

27%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 3

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 9

Vulnerabilities 0

Is Reversecore MCP safe?

Public supply-chain signals for Reversecore MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Reversecore MCP carries less obvious unverified-evidence risk than projects with thin signals.

Does Reversecore MCP publish package provenance?

Yes. Reversecore MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Reversecore MCP have an OpenSSF Scorecard?

Reversecore MCP has an OpenSSF Scorecard score of 5.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 Reversecore MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Reversecore MCP use?

Reversecore MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Reversecore MCP's commits signed?

27% of the last 100 commits to Reversecore 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

Reversecore MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Redis

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

2 tags

Broad capability areas detected.

code
database

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 Reversecore MCP?

For maintainers

HVTrust scores Reversecore 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

2026-08-31

Rank Moved

Rank dropped 16 spots (#106 → #122)

2026-08-29

Scorecard Added

OSSF Scorecard: 5.7/10

2026-08-29

Grade Changed

Trust grade C → B

2026-08-29

Rank Moved

Rank rose 156 spots (#268 → #112)

2026-08-29

HVTrust Changed

HVTrust up 11.8pts (64.6 → 76.4)

2026-08-26

Rank Moved

Rank dropped 16 spots (#246 → #262)

2026-08-24

Rank Moved

Rank dropped 12 spots (#233 → #245)

2026-08-22

Grade Changed

Trust grade B → C

2026-08-22

Rank Moved

Rank dropped 27 spots (#214 → #241)

2026-08-22

Activity Score Changed

Activity score down 7pts (68 → 61)

2026-08-19

Rank Moved

Rank dropped 12 spots (#196 → #208)

2026-08-17

Rank Moved

Rank rose 13 spots (#205 → #192)

2026-08-13

Rank Moved

Rank dropped 12 spots (#190 → #202)

2026-08-10

Rank Moved

Rank dropped 12 spots (#184 → #196)

2026-08-08

Newly Listed

First tracked at rank #177

GitHub → PyPI: reversecore-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/reversecore-mcp.svg)](https://hvtracker.net/agents/reversecore-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/reversecore-mcp"><img src="https://hvtracker.net/badge/reversecore-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.3 · Raw JSON