Verfy

MCP servers / mcp-neo4j-cypher

MCP tool changes

mcp-neo4j-cypher

1 of its last 1 updates changed what the agent reads: 0 tool descriptions rewritten, up to 0.6.0.

PyPI package · last recorded on 13 November 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. PyPI page · Method and limits · this data as JSON.

Release by release

0.5.3 → 0.6.0

minor release, 10 April 2026

get_neo4j_schema: input schema changed

Releases tried: 0.4.1 (2025-09-30), did not start; 0.5.0 (2025-11-03), did not start; 0.5.1 (2025-11-07), did not start; 0.5.2 (2025-12-15), did not start; 0.5.3 (2026-02-23); 0.6.0 (2026-04-10).

Tools in 0.6.0

The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition. Verfy 0.16.0 and later also pin a tool's title, annotations and output schema when the server sends them, so such a tool shows a different pin in your lock.

Tools in 0.6.0
ToolDescriptionPin
get_neo4j_schemaReturns nodes, their properties (with types and indexed flags), and relationships using APOC's schema inspection. You should only provide a `sample_size` value if requested by the user, or tuning the retrieval performance. Performance Notes: - If `sample_size` is not provided, uses the server's default sample setting defined in the server configuration. - If retrieving the schema times out, try lowering the sample size, e.g. `sample_size=100`. - To sample the entire graph use `sample_size=-1`.75b287899e15
read_neo4j_cypherExecute a read Cypher query on the neo4j database.63265432d8cd
write_neo4j_cypherExecute a write Cypher query on the neo4j database.31e0f14a3754

Lock these tools

Pin what mcp-neo4j-cypher serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.

$ pip install verfy
$ verfy lock check --update   # shows each tool, then writes verfy.lock
$ git add verfy.lock
# .github/workflows/verfy.yml, after actions/checkout
- uses: verfy-dev/verfy-action@v1

Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.