chore(deps): update dependency mcp-neo4j-cypher to v0.6.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
mcp-neo4j-cypher	0.5.3 → 0.6.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[github-actions]

🔒 MCP Security Scan Results

✅ mcp-neo4j-cypher

• Status: Passed
• Tools scanned: 3
• Result: No security issues detected

---

Summary: Scanned 1 MCP server(s), all passed security checks. ✅

[rdimitrov]

@renovatebot rebase

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[JAORMX]

Triage: build-containers blocked by genuine upstream CVEs

Local Grype scan (DB 2026-04-27) of the 0.6.0 image surfaces these HIGH/CRITICAL findings (severity-cutoff: high, only-fixed: true):

Package	Installed	GHSA	Severity	Fixed in
fastmcp	2.13.3	GHSA-vv7q-7jx5-f767	Critical	3.2.0
fastmcp	2.13.3	GHSA-rww4-4w9c-7733	High	3.2.0
fastmcp	2.13.3	GHSA-5h2m-4q8j-pqpj	High	2.14.2
fastmcp	2.13.3	GHSA-rcfx-77hg-w2wv	High	2.14.0
mcp	1.22.0	GHSA-9h52-p55h-vw2f	High	1.23.0

These are genuine upstream CVEs, not false positives. The fastmcp findings are blocked by the package's own constraint fastmcp<2.14,>=2.10.5 (note: 0.5.3 had fastmcp<3 which actually allows the 3.2.0 fix) — so 0.6.0 narrows the dep range and introduces 2 additional HIGH-severity vulns (GHSA-5h2m-4q8j-pqpj, GHSA-rcfx-77hg-w2wv) compared to the currently-shipped 0.5.3.

Recommendation: Hold this bump. Upstream needs to widen fastmcp to allow 3.x, or backport fixes to 2.13.x. Tracking issue in neo4j-contrib/mcp-neo4j is appropriate.