Checking remote desktop exposure
Priya Sharma, security engineer at BigCo, asked how many of the company's IPs exposed RDP. Memtro ran a free count with port and organisation facets, then read one flagged host's open ports, products and known CVEs.
What does our office IP range expose to the internet?
Shodan tells you what your addresses show the internet. You see what an IP exposes, with open ports, products, versions, known CVEs, hostnames and owner, plus searches and free counts with facets over Shodan's index, a domain's DNS records, network alerts, scans and your plan's credits. When asked and granted, Memtro can create, change and delete network alerts, turn their triggers on or off, ignore a service, route an alert to an existing notifier and request a scan of your own IPs. Worth knowing: scans need a paid API plan and spend credits Shodan does not refund.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Shodan tool, reads what it needs, and answers with the source cited.
These tools change something in Shodan. 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 Shodan 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.
What does our office IP range expose to the internet?
How many of our IPs expose RDP?
Which known CVEs does Shodan list for 203.0.113.10?
Which subdomains of acme.example has Shodan seen?
How many scan credits do we have left?
Priya Sharma, security engineer at BigCo, asked how many of the company's IPs exposed RDP. Memtro ran a free count with port and organisation facets, then read one flagged host's open ports, products and known CVEs.
Tom Reilly, IT manager at Northwind, asked Memtro to watch the office range. Memtro created a network alert, turned on the new service and vulnerable triggers, and attached the team's existing Slack notifier. The people that channel reaches are now told when one fires.
The teams that lean on Shodan most, a question each of them asks, and what they connect beside it.
A record in Shodan 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.
Sign in at account.shodan.io and copy the key from Account Overview. Your Shodan plan decides what is allowed.
In Memtro, open Connections → Shodan and paste it into API key.
An administrator grants the actions by name, such as Request scan or Enable alert triggers, to the teams that may use them.
Ask what your office IP range exposes to the internet.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Shodan tools are the same everywhere.
Only when you ask, and only what it has been granted: create a network alert to monitor IPs or ranges; change the networks an alert monitors; delete a network alert (permanent); turn alert triggers on (notifications start); turn alert triggers off; ignore a service for an alert trigger; stop ignoring a service for an alert trigger; send an alert's notifications to an existing notifier; stop sending an alert to a notifier; request an on-demand scan of IPs (spends scan credits, probes those addresses). 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. Sign in at account.shodan.io and copy the key from Account Overview. Your Shodan plan decides what is allowed.
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