Open high findings
Priya Sharma, a security engineer at Northwind, asked which high-severity findings were still active on the main site. Memtro listed them with host, CVSS score, OWASP class and when each was first detected.
Which high-severity findings are still active on our main site?
Detectify scans your external attack surface and web applications. Memtro reads findings by status, severity, source, asset and host, with CVSS, CWE and OWASP class and when each was first and last seen, one finding in full, root assets and subdomains, and scan profiles with their latest scan and schedule. When asked and granted, it can start, stop and schedule scans, mark findings fixed, accepted risk or false positive, add and delete assets, and invite members. The captured request, response and cookie behind a finding are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Detectify tool, reads what it needs, and answers with the source cited.
These tools change something in Detectify. 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.
Once Detectify 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 high-severity findings are still active on our main site?
What new findings has surface monitoring raised since Monday?
Which subdomains of acme.com were discovered this month?
When did the last scan of the checkout profile run, and did it finish?
Start a scan on the checkout profile.
Priya Sharma, a security engineer at Northwind, asked which high-severity findings were still active on the main site. Memtro listed them with host, CVSS score, OWASP class and when each was first detected.
Tom Reilly, an application security lead at Acme Ltd, asked Memtro to scan the checkout profile once a fix was deployed. Memtro started the scan, then read the profile to show him it was running.
The teams that lean on Detectify most, a question each of them asks, and what they connect beside it.
A record in Detectify 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.
In Detectify, open Team settings → API keys and create a key for API v2 with the secret key left off, since a key made with one is refused.
In Memtro, open Connections → Detectify and paste the API key.
An administrator grants the scan, finding and asset actions by name to the teams that may use them, and keeps invitations to those who manage access.
Ask which high-severity findings are still active on your main site.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Detectify tools are the same everywhere.
Only when you ask, and only what it has been granted: start an Application Scan on a scan profile (scans the company's own site); stop a running scan; schedule scans on a scan profile; remove a scan profile's schedule; mark a finding fixed, accepted risk or false positive; clear a finding's fixed, accepted risk or false positive status; add an asset (domain or IP) to the team; delete an asset from the team (permanent); invite people to the Detectify team. 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 key. In Detectify, open Team settings → API keys and create a key for API v2 with the secret key left off, since a key made with one is refused.
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