Is MCP Neo4j safe to use?

MCP Neo4j has an HVTrust score of 55.4/100 (Grade C), ranked #767 of 1325 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 55.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 986 GitHub stars and is categorized under MCP Servers.

MCP Neo4j

neo4j-contrib/mcp-neo4j

Neo4j Labs Model Context Protocol servers

MCP Servers Python Listed MIT

Is MCP Neo4j safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.5 / 10

Provenance None

Signed commits 97%

Last push 17d ago

Compare MCP Neo4j

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

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

How MCP Neo4j compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP Neo4j’s 55.4.

Where the 55.4 comes from

HVTrust dimensions vs the MCP Servers average

55.4 / 100 · 100.0% confidence

MCP Neo4j MCP Servers average (775 agents)

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

9.2 / 25

1.1 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.5 / 17

0.7 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

12.8 / 20

0.7 above avg 12.1

AdoptionLog-scaled stars · package downloads

9.1 / 20

1.9 above 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-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

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.5/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.

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

58.0

Activity sub-score · out of 100

#424

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 C 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-26

Activity & Reach

Stars

986

Forks

260

Last Push

2026-09-09

17 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲4

was #771

Analysis

Activity Inputs

58.0 / 100

StarsRepository reach

18.0 / 30

FreshnessLast push recency

22.6 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

11.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.5 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

97%

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 1

Packaging -1

Pinned-Dependencies 0

SAST 4

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about MCP Neo4j

MCP Neo4j has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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.5/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?

Maintained. Last push was 17 days ago.

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?

97% 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

How this surface has changed

Detected changes to MCP Neo4j'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

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-09

Activity Resumed

Activity resumed

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

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

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 rose 204 spots (#963 → #759)

2026-09-23

HVTrust Changed

HVTrust up 30.1pts (25.6 → 55.7)

2026-09-22

Newly Listed

First tracked at rank #963

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank rose 30 spots (#767 → #737)

2026-09-17

Rank Moved

Rank rose 11 spots (#778 → #767)

2026-09-10

Rank Moved

Rank dropped 46 spots (#707 → #753)

2026-09-09

Activity Resumed

Activity resumed

2026-09-09

Grade Changed

Trust grade D → C

2026-09-09

Rank Moved

Rank rose 334 spots (#1041 → #707)

2026-09-09

HVTrust Changed

HVTrust up 12.0pts (44.4 → 56.4)

2026-09-09

Activity Score Changed

Activity score up 27pts (33 → 60)

2026-09-08

Rank Moved

Rank dropped 15 spots (#1026 → #1041)

2026-09-07

Rank Moved

Rank dropped 29 spots (#997 → #1026)

2026-09-06

Rank Moved

Rank dropped 11 spots (#986 → #997)

2026-09-05

Rank Moved

Rank dropped 70 spots (#916 → #986)

2026-09-04

Rank Moved

Rank dropped 30 spots (#886 → #916)

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