Which critical dependency alerts are open in the web repo?
Socket answers which dependencies put your code at risk. You see repositories, full scans, open and cleared alerts with package, severity, CVE, reachability and fix, triage rules, alert resolutions and repository labels. When asked and granted, Memtro can add, edit or remove repositories, manage repository labels, set or delete triage rules, resolve alerts by a named scope or undo it, and rescan or delete full scans. Socket can tell Memtro when a pull request scan finishes or an alert is raised or cleared, and a job can start on it. Only an organisation admin can create the token.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Socket tool, reads what it needs, and answers with the source cited.
These tools change something in Socket. 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 Socket for you. Each event can start a job, with the event as its input. Socket signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Socket 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 alerts are open in the web repo?
Which open alerts are on known-exploited CVEs?
When did the last full scan of the api repository's main branch run?
Which triage rules apply to lodash?
How much API quota is left this hour?
Priya Sharma, security engineer at BigCo, asked which critical alerts were open in the web repository. Memtro listed each with its package and version, CVE, reachability and fix, and showed which were direct dependencies.
At Acme Ltd, a job starts when Socket reports a pull request scan finished. Memtro reads the open alerts for that repository and tells Dan Fletcher, the tech lead, which high severity ones are reachable.
The teams that lean on Socket most, a question each of them asks, and what they connect beside it.
A record in Socket 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 the Socket dashboard, an organisation admin goes to Settings, then API Tokens, creates a token and ticks the list scopes, plus the write scopes for the actions you want.
In Memtro, open Connections → Socket and paste it into API token. Leave Organisation slug blank when the token belongs to one organisation.
An administrator grants the actions by name, such as Resolve alerts or Delete full scan, to the teams that may use them. Events are turned on from the connection's Events tab.
Ask which critical alerts are open in the web repository.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Socket tools are the same everywhere.
Only when you ask, and only what it has been granted: add a repository to Socket; edit a repository's name, description, visibility, default branch or archived state; remove a repository from Socket; create a repository label; apply a label to a repository; remove a label from a repository; delete a repository label; create or change an alert triage rule; delete an alert triage rule; resolve the alerts matching a named scope; undo an alert resolution; rescan a full scan; delete a full scan. 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.
API token. In the Socket dashboard, an organisation admin goes to Settings, then API Tokens, creates a token and ticks the list scopes, plus the write scopes for the actions you want.
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 Socket 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
