Evo MCP Server now available
Snyk's Evo tool now integrates with MCP clients like Claude, Codex, and Cursor, allowing users to query their AI assets, visualize connections, review policies, and manage policy violations directly from their agent. Users can discover AI assets across code, developer machines, and pentest targets without leaving their workflow.
You can connect any MCP client, such as Claude, Codex or Cursor, to Evo and ask about your AI estate from the agent you already work in.
What's new. You can now:
Ask what AI assets Evo has discovered across your code, your developer machines, and your pentest targets
See how those assets connect, for example which MCP servers an agent uses or which findings came from a target
Read your policies and the violations open against them
Create and update policies without leaving your agent
To get started, check out our documentation
Source: original entry ↗
More from Snyk
Follow Snyk to get its new changes in your feed and email digest.
Snyk CLI v1.1308.1 released
HTML report output is now available by default without preview features, and project names are consistently displayed in test summaries. This release also patches multiple security vulnerabilities.
Pending ignore requests now visible on Project's Issues page
Issues with pending ignore requests now display a clear "Pending Ignore Request" status on the Issues page and in issue details, with filtering support. The issues API now reports pending as part of an issue's ignore status for programmatic distinction of open, pending, and ignored findings.
Snyk Code October update: improved analysis and more findings
Snyk Code now analyzes projects more deeply and accurately across Java, Kotlin, Go, TypeScript, JavaScript, Python, C#, PHP and Ruby, with significantly more findings reported. Improvements include better import resolution via config files, corrected PHP typing, expanded library coverage, new vulnerability detection rules, and enhanced template and serverless application analysis.