updated 2026-11-10 04:07 UTC

MCP Neo4j

Repository Website

Neo4j Labs Model Context Protocol servers

MCP Servers Python Listed MIT

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

OSSF Scorecard 3.5 / 10
Provenance None
Signed commits 97%
Last push 62d 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 51.0/100 (Grade C), ranked #978 of 1374 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 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 MCP Neo4j 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/neo4j-contrib/mcp-neo4j, MIT, last pushed 2026-09-09. 97% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.5/10 (scanned Oct 26, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review3
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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

  3. Published packages Not linked

    Without a build attestation, nothing proves the published files were built from this repository.

Changes to this chain

  • 2026-08-26 OSSF Scorecard: 3.4/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 MCP Neo4j’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 MCP Neo4j compares in MCP Servers

  1. #548 TradeOS 51.1 +0.1
  2. #549 Ros2 MCP 51.0 ±0
  3. #550 MCP Neo4j 51.0 this agent
  4. #551 MCP Server Motherduck 51.0 ±0
  5. #552 Greptimedb MCP Server 50.9 −0.1

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

Where the 51.0 comes from

HVTrust dimensions vs the MCP Servers average

51.0 / 100 · 100.0% confidence

MCP Neo4j MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.2 / 25
1.6 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.5 / 17
0.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
7.9 / 20
4.3 below avg 12.2
AdoptionLog-scaled stars · package downloads
9.6 / 20
2.0 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-30
Rank Moved
Rank dropped 10 spots (#964 → #974)
2026-10-17
Rank Moved
Rank dropped 10 spots (#924 → #934)
2026-10-16
Rank Moved
Rank dropped 13 spots (#911 → #924)
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.
Refresh maintenance signals The repo was last pushed 62 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
45.7
Activity sub-score · out of 100
#550
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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 62 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
989
Forks
261
Last Push
2026-09-09
62 days ago
Commits (4 wk)
0
Downloads (7d)
62
pypi
HN mentions (30d)
—
Open Issues
17
Rank Change
▲7
was #985

Analysis

Activity Inputs

45.7 / 100
StarsRepository reach
18.0 / 30
FreshnessLast push recency
16.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
11.2 / 20

Common questions about MCP Neo4j

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.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?
Slowing down. Last push was 62 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?
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.
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
Rank 28HVTrust 3Grade 2Scorecard 1Score 1Fresh 1Delisted 1Listed 1MCP 1Surface 1
2026-10-30
Rank Moved
Rank dropped 10 spots (#964 → #974)
2026-10-17
Rank Moved
Rank dropped 10 spots (#924 → #934)
2026-10-16
Rank Moved
Rank dropped 13 spots (#911 → #924)
2026-10-15
Rank Moved
Rank dropped 12 spots (#899 → #911)
2026-10-12
Rank Moved
Rank dropped 11 spots (#879 → #890)
2026-10-09
Rank Moved
Rank dropped 51 spots (#815 → #866)
2026-10-08
Rank Moved
Rank dropped 21 spots (#794 → #815)
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)
GitHub → Website → PyPI: mcp-neo4j-aura-manager

Embed Badge Badge guide for maintainers →

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