Shadow integrations
Detect unsanctioned MCP connections
Surf ingests every MCP connection users create, flags any integration that falls outside policy, and ties it to the person who set it up.
The gap
AI adoption is outpacing your visibility.
As teams connect Claude to more tools and data, security loses track of what has been wired up, who set it up, and what it can reach. A single unsanctioned connection can quietly become a path for sensitive data to leave the business, or for Claude to touch systems it was never meant to access.
Surf closes that gap. It reads how Claude is actually used, ties every signal to the person responsible, and shows the reach before a convenience becomes an incident.
Use cases
Shadow integrations
Surf ingests every MCP connection users create, flags any integration that falls outside policy, and ties it to the person who set it up.
Offboarding
When someone is terminated, Surf surfaces the Claude access and connections still tied to them, so nothing stays open behind them.
Data exposure
Surf watches when sensitive content moves outside the organization and routes the finding to an owner who can act on it.
How it works
Signal
Surf pulls Claude telemetry from the Anthropic Compliance API as it happens.
Context
Every signal is mapped to an accountable owner and its blast radius is modeled.
Execution
The finding lands with the person who can remediate it, with the context to act.
All of it runs inside the Context Graph, the system of record that connects identities, assets, and access across your environment.
Built on the Anthropic Compliance API
See how Claude is used across the business, not in a quarterly snapshot but as it changes.
Every finding is mapped to an accountable owner, so it moves toward a fix instead of a backlog.
Know what is actually at risk, so teams can act on what matters before it spreads.
Surf × Anthropic
See how Surf turns Claude usage into owned, actionable signal.