Is MCP Neo4j safe to use?

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

What is the trust score for MCP Neo4j?

MCP Neo4j scores 45.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 981 GitHub stars and is categorized under MCP Servers.

MCP Neo4j

neo4j-contrib/mcp-neo4j

Neo4j Labs Model Context Protocol servers

MCP Servers Python Grade D Listed MIT

45.3/100

Rank #902 of 1320

Compare MCP Neo4j

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-04-10 · 147d ago

Recent change

Rank +7

Is MCP Neo4j safe? MCP Neo4j scores 45.3/100 (Grade D), ranked #902 of 1320 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 3.4/10; 98% of recent commits are signed; last pushed 2026-04-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#487 Word MCP Live — 45.5 (D) → #488 Home Assistant Vibecode Agent — 45.3 (D) → #490 Kolada MCP Server — 45.2 (D) → #491 MCP Mermaid — 45.2 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-04

Rank Moved

Rank dropped 16 spots (#886 → #902)

2026-09-03

Rank Moved

Rank dropped 50 spots (#836 → #886)

2026-09-02

Rank Moved

Rank dropped 47 spots (#789 → #836)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.4/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.

Refresh maintenance signals The repo was last pushed 147 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for MCP Neo4j View MCP Servers Report missing data

33.9

Activity sub-score · out of 100

#489

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

981

Forks

257

Last Push

2026-04-10

147 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼16

was #886

Analysis

HVTrust Dimensions vs MCP Servers

45.3 / 100 · 100.0% confidence

MCP Neo4j MCP Servers average (778 agents)

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

9.2 / 25

in line with avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.4 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

2.2 / 20

10.0 below avg 12.2

AdoptionLog-scaled stars · package downloads

9.7 / 20

3.5 above avg 6.2

Activity Inputs

33.9 / 100

StarsRepository reach

18.0 / 30

FreshnessLast push recency

4.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

11.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.4 / 10

OpenSSF Scorecard · scanned Sep 2, 2026

Signed Commits

98%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 8

CII-Best-Practices 0

Code-Review 3

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 4

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is MCP Neo4j safe?

Public trust evidence for MCP Neo4j 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 MCP Neo4j publish package provenance?

No published build provenance is currently detected for MCP Neo4j. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Neo4j have an OpenSSF Scorecard?

MCP Neo4j has an OpenSSF Scorecard score of 3.4/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 MCP Neo4j actively maintained?

Slowing down. Last push was 147 days ago — keep an eye on whether activity resumes.

What license does MCP Neo4j use?

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

Are MCP Neo4j's commits signed?

98% of the last 100 commits to MCP Neo4j 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

MCP Neo4j 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.

Google Gemini

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

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain MCP Neo4j?

For maintainers

HVTrust scores MCP Neo4j 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-09-04

Rank Moved

Rank dropped 16 spots (#886 → #902)

2026-09-03

Rank Moved

Rank dropped 50 spots (#836 → #886)

2026-09-02

Rank Moved

Rank dropped 47 spots (#789 → #836)

2026-09-01

Rank Moved

Rank dropped 32 spots (#757 → #789)

2026-08-31

Rank Moved

Rank dropped 35 spots (#722 → #757)

2026-08-30

Rank Moved

Rank dropped 26 spots (#696 → #722)

2026-08-29

Rank Moved

Rank dropped 46 spots (#650 → #696)

2026-08-28

Rank Moved

Rank dropped 19 spots (#631 → #650)

2026-08-27

Rank Moved

Rank dropped 15 spots (#616 → #631)

2026-08-26

Scorecard Added

OSSF Scorecard: 3.4/10

2026-08-26

Rank Moved

Rank rose 205 spots (#821 → #616)

2026-08-26

HVTrust Changed

HVTrust up 19.4pts (26.5 → 45.9)

2026-08-16

Rank Moved

Rank dropped 15 spots (#802 → #817)

2026-08-13

Rank Moved

Rank dropped 10 spots (#789 → #799)

2026-08-10

Rank Moved

Rank dropped 44 spots (#752 → #796)

2026-08-08

Newly Listed

First tracked at rank #748

GitHub → PyPI: mcp-neo4j-aura-manager

Embed Badge Badge guide for maintainers →

For maintainers

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