Open vulnerabilities by severity, package and project, with whether a fix exists.
Connect Snyk with an API token and Memtro reads your organisations, every project Snyk scans with its issue counts, open and resolved issues by severity, type, project and date with the vulnerable package or file and whether a fix exists, and one issue in full with its CVEs. The hourly sync writes each new critical or high issue into memory. When asked, and once an administrator has granted each action by name, it ignores or un-ignores an issue, changes a project's settings and owner, and groups projects into collections. Deleting a project or target removes its findings history permanently.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Snyk tool, reads what it needs, and answers with the source cited.
These tools change something in Snyk. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Snyk for you. Each event can start a job, with the event as its input. Snyk signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Snyk is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which critical issues in the api repo have an upgrade available?
How many open high-severity vulnerabilities do we have, and which package has the most?
What was found in the last 7 days across all projects?
Give me the full detail and remedies for the lodash prototype pollution issue
Ignore the minimist issue in the build-tools project for 30 days: it is not reachable at runtime
A release manager asks whether anything critical is open in the checkout service before Thursday's deploy. Memtro lists the open critical and high issues in that project, each with the package, the fix available and the CVE, so the upgrade goes in first.
Kate Morgan reviews a high issue in a build-only dependency and asks Memtro to ignore it for 30 days. Memtro ignores it in that project with her reason and the expiry, attributed to the token's owner, so it stops counting in the project's results until the date passes or someone removes the ignore.
The teams that lean on Snyk most, a question each of them asks, and what they connect beside it.
A record in Snyk is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn Snyk open Account settings → Personal access tokens → Generate new token, or make a service account under Settings → Service accounts. A group-level Group Viewer token keeps Memtro to reading, and the actions need a token whose role may change those projects
Copy the token: it is shown once. A personal access token expires within 90 days and a service account token does not. The REST API needs the Enterprise plan
In Memtro open Connections → Snyk, paste the API token, add the organisation id (Settings → General → Organization ID) if the token sees several, and the region URL for an EU, Australian or US-02 tenant, and connect
Ask which critical issues with an upgrade available are open in your production projects
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Snyk tools are the same everywhere.
Only when you ask, and only what it has been granted: ignore an issue in a project, with a reason and an optional expiry; remove an ignore so the issue counts again; change a project's business criticality, environment, lifecycle, tags, test frequency or owner; delete a project and its findings history; delete a target and every project under it; create a collection; add projects to a collection. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Snyk records into memory as entities.
API token. In Snyk open Account settings → Personal access tokens → Generate new token, or make a service account under Settings → Service accounts. A group-level Group Viewer token keeps Memtro to reading, and the actions need a token whose role may change those projects.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Snyk for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
