Security scanner
The validation layers applied to MCP servers and what the verified badge means.
The MCP Security Scanner analyzes the servers registered in the organization before they reach workspaces.
It exists because an MCP isn't passive content: it is code the Agent can call against real systems. Registering a server is a security decision, not a catalog one.
Where each thing lives
The configuration and the result live on different screens:
- Settings › General defines which validation layers the scanner applies in the organization.
- MCPs shows the result. Each server has the View security action, which opens that item's analysis.
An approved server gets a verified badge in the list, visible without opening the details.
How to read the result
The badge answers a single question: whether the server passed the configured layers. It doesn't claim the server is safe for your use case.
Two things the scanner doesn't know:
- What the server does with the data the Agent sends it.
- Whether the exposed tools are appropriate for the people in that workspace.
The badge is a necessary condition, not a sufficient one. A verified server from an unknown vendor is still an unknown vendor with write access to your systems.
Adjust the layers
Under Settings › General, the MCP Security Scanner section lists the available layers and lets you turn each one on or off.
Loosening the layers lets more servers through; tightening them may fail servers that were already in use. The change applies to the whole organization, and only the Superadmin can make it.
Next steps
- Register servers in Register a server.
- See the screen's other sections in Settings.