Agent Scan is an MCP server that security scanner for AI agents, MCP servers and agent skills. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 63/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"agent-scan": {
"args": [
"snyk-agent-scan"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Discover and scan agent components on your machine for prompt injections and vulnerabilities (including agents, MCP servers, skills).
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'snyk-agent-scan' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked snyk-agent-scan against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.
BridgeGuard MCP Server - Cross-chain bridge security audit tools for AI coding agents. Scan bri...
Regression testing for MCP servers. Checks capabilities, invokes tools, detects schema drift.
MCP Security Weekly
Get CVE alerts and security updates for Agent Scan and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Discover and scan agent components on your machine for prompt injections
and vulnerabilities (including agents, MCP servers, skills).
Note: CLI output is experimental and subject to change
Agent Scan v0.5.x (planned for deprecation)
The raw output of this CLI — including issue codes, field names, severity labels, and response structure — is experimental and may change without notice between releases. We do not recommend building production workflows that depend on specific CLI output fields or issue codes.
Agent Scan v0.6 and later
The raw output of this CLI — including risk indicator names, scores, field names, and response structure — is experimental and may change without notice between releases. We do not recommend building production workflows that depend on specific CLI output fields or risk names.
If you are an enterprise customer using Snyk to manage agent security risk at scale, the CLI output may not reflect what is sent to and shown in the Evo platform. The underlying integration, discovery, and risk assessment that powers enterprise deployments is stable and supported — any changes will be communicated in line with standard Snyk product practices. Contact your account team for deployment guidance.
NEW Read our technical report on the emerging threats of the agent skill eco-system published together with Agent Scan 0.4, which adds support for scanning agent skills.
[!WARNING] Agent Scan v0.5.x uses issue-code output. This CLI line is planned for deprecation.
Agent Scan helps you discover all your installed agent components (harnesses, MCP servers, and skills) and scans them for common threats like prompt injections, sensitive data handling, or malware payloads hidden in natural language. Ignore analysis on skills by using --no-skills.
⚠️ IMPORTANT: Scanning MCP configurations will execute the commands defined in them.
When Agent Scan scans an MCP configuration file, it starts the stdio MCP servers by executing the commands and arguments specified in the config. This is necessary to retrieve tool descriptions and perform security analysis.
Recommendations:
- Run scans inside a sandbox (Docker container, VM, or disposable environment) when evaluating untrusted or third-party MCP configs
- Review the consent prompt carefully during interactive scans, it shows the exact command and arguments that will be executed for each server
- Use
--dangerously-run-mcp-serversonly in trusted environments where you've verified all MCP server commandsBy default, Agent Scan requires explicit user consent (y/n) before starting each stdio MCP server during interactive runs. This gives you control over what gets executed on your system.
Choose one of two ways to run Agent Scan:
uvx using the instructions below.