MCP Server Security

MCP server scanning and testing

Scanners that check MCP servers include Cisco's MCP Scanner and Snyk's Agent Scan, both Apache-2.0 open source, plus OWASP's named mcp-scan. They read tool metadata and packages, so they miss behavior hidden behind unchanged definitions. Test your own servers for token, Origin and input handling. Sources were read on 16 Nov 2026.

Facts read on .

Which scanners check MCP servers?

Several open-source and vendor scanners check MCP servers, and two documented ones carry Apache-2.0 licenses. Cisco's MCP Scanner scans a server's tools, prompts, resources and instructions with YARA rules and LLM-based analysis, and has a mode that reads servers from well-known client config locations on the machine. Snyk's agent-scan README lists a per-operating-system table of clients it reads, including Claude Desktop, Claude Code, Cursor and VS Code.

OWASP's cheat sheet names mcp-scan for detecting poisoned descriptions and cross-server shadowing, and Backslash Security runs a free MCP Server Security Hub that scores servers without a login.

Each tool answers a different question. Cisco's scanner reads server contents, Snyk's reads client configs on a machine to find servers, and a hub score summarizes a public server. Pick by the question you need answered, and expect to combine two.

Sources: Cisco AI Defense MCP Scanner repository; Snyk agent-scan README; OWASP MCP Security Cheat Sheet; Backslash Security: MCP Server Security Hub.

What do scanners miss?

Scanners miss behavior that is not visible in the metadata or code they read. OWASP states that hashing a tool definition detects metadata changes, not changes to server code or behavior behind an unchanged definition, and that filters for injected instructions cannot establish that the remaining text is safe.

Coverage gaps matter too. The MCP Registry delegates code scanning to others, and Snyk's supply chain documentation admits that a stdio server not yet in its catalog ends as discovery only, with no risk assessment. Ask any scanner what it does with a server it has never seen.

Sources: OWASP MCP Security Cheat Sheet; MCP Registry: About; Snyk documentation: Agent Supply Chain Security.

Where do you run scans?

Run them at three points: when a server is proposed, on every laptop on a schedule, and in CI for servers you build. Proposal-time scans feed the catalog review, and scheduled laptop scans catch servers added outside the process.

Snyk's deployment documentation says its scheduled discovery scan runs every 24 hours by default on macOS and Windows, with the installer pushed by Jamf Pro or Intune. Cisco's MCP Scanner is a command-line tool, and its DefenseClaw documentation describes an enterprise edition deployed with a package or an MDM. Pick the cadence that matches how fast your developers add servers.

Sources: Snyk documentation: Activation and deployment; Cisco AI Defense MCP Scanner repository; Cisco DefenseClaw documentation: support matrix.

How do you test a server you build?

Test it with an MCP client you control, and write automated checks for the behaviors the specification requires. The MCP Inspector is the usual manual client, and its own advisory is a reminder to keep it patched: versions below 0.14.1 allowed unauthenticated requests to launch MCP commands over stdio (CVE-2025-49596).

Automate these expectations in CI:

Sources: GitHub advisory GHSA-7f8r-222p-6f5g: Inspector proxy server vulnerabilities (CVE-2025-49596); MCP specification: Authorization (2025-11-25); MCP specification: Transports (2025-11-25); OWASP MCP Security Cheat Sheet.

How do you act on scan results?

Treat a finding as a reason to review, not as a verdict. Map each finding to a register row, decide whether the control already exists, and record the outcome in the catalog entry. A clean scan supports approval but does not replace the code review for a server with file or shell access.

Sources: OWASP MCP Security Cheat Sheet.

Sources