Scans
Run your first scan
Add an MCP server, mark it as a production server, scan it from MCP Scan, and read its score, categories and findings.
An MCP Scan checks a deployed MCP server in four categories and rolls them into one score out of 100, with a fix for every problem it finds. Scans run from your account, and every run is saved to your scan history.
Before you start
- Scan a deployed server. MCP Scan connects to the server's URL from Guardian Samurai's cloud, so the server must be reachable from the internet. Test a server that's still in development from your own machine with the CLI instead.
- Only scan servers you own or have permission to scan. A scan calls only tools that are marked or recognized as read-only. It never calls a tool that may change data.
- The Evaluation category uses AI. It sends the server's tool descriptions and the results of read-only tool calls to an AI provider.
Step 1: Add the server
- Select Samurai Quality in the header. It opens MCP Servers.
- Select Add new.
- Enter a Label, such as
GitHub production. This is the name the server goes by in your lists and history. - Paste the server's URL, such as
https://example.com/mcp, or its JSON configuration, such as{"mcpServers":{"github":{"url":"https://example.com/mcp","headers":{"Authorization":"Bearer <token>"}}}}. If your server needs a token, include it in the JSON headers. If the JSON already names the server, that name fills in the label. - Check Production server. Only production servers can be scanned from the web app.
- Select Save server. It appears in the list with a green Production chip.
Secrets you save, such as tokens in the URL or headers, are stored encrypted. When you edit the server later, you see the secrets you typed yourself; teammates see •••••••• in their place. Everyone in your organization can scan a saved server. See Setup Details for what Set as CLI default does.
Already saved the server without checking Production server? Select Edit on its row, check the box and save.
Step 2: Scan it
- Go to MCP Scan in the Samurai Quality menu on the left.
- Find your server in the Production servers table. Its Last scanned and Scanned by columns show when it was last scanned and by whom.
- Select Scan on its row.
The results fill in on the same page while the scan runs. The table's Last scanned updates, and the run is added to Scan history when it finishes.
The four categories
Each category answers one question about the server.
- Integration: does the system respond? The connection, the MCP handshake, tool discovery and protocol behavior.
- Unit: does each tool work? Each tool's definition, and calls to the read-only tools with valid input.
- Evaluation: can an AI use it well? Whether an AI model picks the right tool, fills in the right parameters and gets a useful answer, including over several steps.
- Security: is it safe to connect to? Transport, authentication and tool safety.
Reading the results
MCP Scan Score. The gauge shows the score out of 100 and a grade:
- Production ready: 85 or above
- Good: 70 to 84
- Needs work: 50 to 69
- Not ready: below 50
If a category couldn't be scored, or fewer than half of the server's tools could be called safely, the grade is capped at Good and the gauge says why. The score itself doesn't change.
Categories. Each category shows its own score and a bar for every check, so you can see where points were lost.
Findings. Only problems are listed, each with how to fix it. The points next to a finding are how much the score would rise once it's fixed. Text marked as AI-generated comes from the server's own descriptions and isn't verified by Guardian Samurai.
Report. A summary of what the server does and what's working. Select Download to save the report as a PDF, CSV or HTML file.
Scan history
Every scan is saved to Scan history at the bottom of the MCP Scan page, with its overall score and the score of each category. Select a date to open that run's full report. Recent scans also appear on your Dashboard.