Neo4j Memory (official)
Last tested 2026-10-22
Score 60/100 · Last tested 2026-10-22 · Version tested 0.4.5 · Package mcp-neo4j-memory · Repo neo4j-contrib/mcp-neo4j
Summary: Neo4j Memory (official) requires credentials or a backing service before it will list tools.
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | uv pip install mcp-neo4j-memory (Python venv, Linux) succeeded in 0s. |
| handshake | fail | 0 | Server did not complete the handshake without credentials or a backing service (to ResolvedIPv4Address(('127.0.0.1', 7687)) (reason [Errno 111] Connect call failed ('127.0.0.1', 7687)) exited code 1). |
| maintenance | partial | 15 | Repo pushed 42 days before test. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (PyPI long_description (package README)). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Not yet tested (no tools/list response without credentials).
Not tested
We did not test behavior with real credentials, security, or performance under load. These are planned; see methodology.
Tools listed
Not available (handshake did not complete without credentials).
Config used in our test
{
"mcpServers": {
"neo4j-memory-official": {
"command": "uvx",
"args": [
"mcp-neo4j-memory"
]
}
}
}FAQ
Is Neo4j Memory (official) deprecated?
No. mcp-neo4j-memory was not deprecated or archived when we last tested it on 2026-10-22.
What replaces Neo4j Memory (official)?
Nothing; Neo4j Memory (official) is not deprecated as of 2026-10-22.
Does Neo4j Memory (official) need an API key?
Unknown. It did not complete the handshake in our test without credentials or a backing service, and gave no clear credential message.
Embed the badge
The badge always shows the current score; payment never changes it.