Salt Surface · See your external exposure See your agentic attack surface the way attackers do.
AI is moving from chatbots that answer to agents that act, and every meaningful AI action ultimately becomes an API call. Salt Surface scans from the outside to reveal the exposed APIs, MCP servers and agentic entry points attackers can already see. Nothing to deploy, configure or integrate.
“We had no idea so many of our APIs were externally visible. With Salt, we identified the risk in minutes.”
CISO · Global bank
The problem
Agents are going live faster than anyone can see what they expose.
Every agent reaches your business through MCP servers and APIs. If you cannot see what is exposed to the internet, you cannot govern it or protect it.
01 Unknown exposed APIs
Teams ship APIs and MCP servers faster than inventories update. Shadow, rogue and forgotten endpoints become the easiest way in.
02 Agentic entry points nobody mapped
Internet-facing agents and MCP servers can reach real systems and data, often with weak or missing authentication.
03 Attack surface tools that do not speak API
Traditional tools count IPs and DNS records. They cannot tell you which of those are APIs, MCP servers or agents, or what they do.
The shift
Stop scanning IPs. See your APIs and MCP servers the way an attacker does.
How it works
From a domain to a map of what attackers can reach, without deploying anything.
Step 01 Start with a domain
Give Salt the domains you own, including subsidiaries and acquisitions. There is nothing to install, no configuration and no traffic to collect.
- Input: your domains
- Deploy: nothing
- Time to first result: minutes
Step 02 Reconstruct from public sources
Salt uses external reconnaissance, like an adversary, to rebuild your exposure from what is already public.
- Mobile apps and their embedded endpoints
- JavaScript and front-end code
- Developer documentation and domains
- Threat intelligence on known exposure
Step 03 Identify what is exposed
Unlike tools that count IPs and DNS records, Salt is built to recognize APIs, MCP servers and agentic entry points, then classify them.
- APIs reachable from the internet
- MCP servers and their auth posture
- Agentic entry points and shadow assets
- Agents and what they can reach
Step 04 Prioritize and go deeper
Exposure is the first layer of depth in the Agentic Security Graph. Add Code, Connect, Collect and Protect to see what was built, how it is configured and what it does at runtime.
- Fix first: exposed and unauthenticated
- Assign: route to an owner
- Go deeper: connect to code, config and runtime
Part of the platform
Exposure is the first layer of depth.
Salt gives you breadth across every agent, MCP server and API, and depth across exposure, source code, configuration and runtime behavior. Surface is where the picture starts.
Capabilities
What you get with Salt Surface.
Agentless, domain-based discovery
Start from your domains. No agents, no traffic collection, no integration work.
Inventory of exposed APIs
A complete list of the APIs reachable from the internet, found the way an attacker would find them.
MCP servers and agentic entry points
Find the MCP servers and agent endpoints exposed outside your perimeter, and see which lack authentication.
Shadow and rogue asset detection
Surface the APIs and MCP servers nobody registered, including those from acquisitions and forgotten projects.
Tech stack and risk signals
See the technology behind each asset and the signals that make it worth fixing first.
Continuous monitoring
Exposure changes daily. Salt keeps mapping, so new assets and drift show up as they appear.
Use cases
Where your team would use it.
M&A exposure assessments
Know what you are inheriting. Map an acquired company’s exposed APIs and MCP servers before the deal closes.
Shadow API detection
Find the APIs and MCP servers that sit outside any inventory, then route them to an owner.
Audit readiness and posture tracking
Show auditors an evidence-based view of external exposure, and track how it improves over time.
Integrations
Start with nothing. Plug into everything you run.
Surface needs no integrations to start. When you are ready, findings flow into the ticketing, chat and SOC tools your teams already use.
Find the APIs and MCP servers
you didn’t know you had.
See your external exposure through an attacker’s eyes. No deployment required.