updated 2026-11-10 04:07 UTC

Reversecore MCP

Repository

A security-first MCP server that empowers AI agents to perform automated reverse engineering, malware analysis, forensics, vulnerability research, and SAST — powered by Radare2, YARA, LIEF, Capstone, and more.

MCP Servers Python Listed MIT

Is Reversecore MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.3 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare Reversecore MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Reversecore MCP scores 84.3/100 (Grade A), ranked #111 of 1374 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 7.3/10; 100% of recent commits are signed; no published advisory affects its latest release (reversecore-mcp); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Reversecore 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 Reversecore 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 Signed

    github.com/sjkim1127/Reversecore_MCP, MIT, last pushed 2026-11-10. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

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

    • Code Review0
    • Branch Protectionn/a
    • Signed Releases2
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies9
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection -1
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 10
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 9
    SAST 10
    Security-Policy 10
    Signed-Releases 2
    Token-Permissions 10
    Vulnerabilities 0

  3. Published packages Linked and attested

    • PyPI reversecore-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: reversecore-mcp 3.0.5. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-29 OSSF Scorecard: 5.7/10

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

  1. #39 AIquila — Nextcloud MCP Server 84.6 +0.3
  2. #40 Markdown Vault MCP 84.5 +0.2
  3. #41 Reversecore MCP 84.3 this agent
  4. #42 Openzim MCP 84.2 −0.1
  5. #43 Semantic Scholar MCP Server 84.1 −0.2

Bars show each HVTrust score; the tick marks Reversecore MCP’s 84.3.

Where the 84.3 comes from

HVTrust dimensions vs the MCP Servers average

84.3 / 100 · 100.0% confidence

Reversecore MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
21.6 / 25
10.8 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
14.7 / 17
2.4 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
18.5 / 20
6.3 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.2 / 20
0.6 above avg 7.6

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-11-10
Rank Moved
Rank rose 10 spots (#121 → #111)
2026-11-09
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-11-09
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
Maintainer Checklist
Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.
Compare with another agent
View MCP Servers Report missing data
66.0
Activity sub-score · out of 100
#41
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 A 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-11-10 04:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
220
Forks
26
Last Push
2026-11-10
today
Commits (4 wk)
41
Downloads (7d)
81
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
▲10
was #121

Analysis

Activity Inputs

66.0 / 100
StarsRepository reach
14.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
20.2 / 25
CommunityFork signal
6.7 / 20

Common questions about Reversecore MCP

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 7.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 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?
100% 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
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface 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
How this surface has changed

Detected changes to Reversecore 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-11-09
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-11-09
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

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
Rank 18Grade 4HVTrust 4Surface 2Score 1Scorecard 1Delisted 1Listed 1Provenance 1MCP 1Surface 1
2026-11-10
Rank Moved
Rank rose 10 spots (#121 → #111)
2026-11-09
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-11-09
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-11-09
Rank Moved
Rank dropped 14 spots (#107 → #121)
2026-10-30
Rank Moved
Rank dropped 15 spots (#79 → #94)
2026-10-27
Rank Moved
Rank dropped 12 spots (#67 → #79)
2026-10-06
Rank Moved
Rank rose 45 spots (#93 → #48)
2026-10-06
HVTrust Changed
HVTrust up 3.1pts (84.5 → 87.6)
2026-09-26
Rank Moved
Rank dropped 13 spots (#92 → #105)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 543 spots (#640 → #97)
2026-09-23
HVTrust Changed
HVTrust up 51.5pts (32.5 → 84.0)
2026-09-22
Newly Listed
First tracked at rank #640
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 21 spots (#109 → #88)
2026-09-13
Grade Changed
Trust grade B → A
2026-09-13
Rank Moved
Rank rose 32 spots (#133 → #101)
2026-09-13
HVTrust Changed
HVTrust up 3.1pts (79.8 → 82.9)
2026-09-05
Rank Moved
Rank dropped 15 spots (#120 → #135)
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)
GitHub → PyPI: reversecore-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 84.3 Grade A
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.4 · Raw JSON