MCP Server Security

MCP security checklist: vet

Eight steps decide whether a server may run: verify the publisher and package name, diff against upstream, review every tool field, scan dependencies, check the SDK against advisories, test in a sandbox, read the launch manifest and record a pinned approval. Each carries controls and sources, read on 16 Nov 2026.

Facts read on .

What this stage covers

Decide whether a server is fit to run before it runs. There are 8 steps here (C-08 to C-15), each a concrete action an engineer can tick.

Sources: OWASP MCP Security Cheat Sheet; Repackaged Amazon SP-API MCP Sends App Secrets to an Undisclosed IP, Knostic; When an MCP Tool Asks for Your GitHub Token, Knostic.

Steps in order

Do these in order; each step lists how to do it and the register risks it closes.

Sources: OWASP MCP Security Cheat Sheet; Repackaged Amazon SP-API MCP Sends App Secrets to an Undisclosed IP, Knostic; When an MCP Tool Asks for Your GitHub Token, Knostic; AI tool poisoning through MCP tool descriptions, CrowdStrike.

Where the settings come from

Setting names appear only where a primary source documents them. Check each against the client version in use before rollout, because the 2026-07-28 MCP revision and client releases changed several defaults.

Sources: OWASP MCP Security Cheat Sheet; Repackaged Amazon SP-API MCP Sends App Secrets to an Undisclosed IP, Knostic; When an MCP Tool Asks for Your GitHub Token, Knostic; AI tool poisoning through MCP tool descriptions, CrowdStrike.

Vet: 8 items

C-08: Verify the publisher and the exact package name

Check the name, publisher and repository against the vendor's own documentation before the first install.

Impact: Look-alike and repackaged packages differ from the real one by a character or an address.

Controls:

  • Compare the package name letter by letter with the vendor's documented install command.
  • Check the publisher account, repository link and release history.
  • Register risks: R-01, R-02.

Severity: high

Sources: OWASP MCP Security Cheat Sheet (read ); Repackaged Amazon SP-API MCP Sends App Secrets to an Undisclosed IP, Knostic (read ).

C-09: Diff the code against the upstream project

For a server that copies an open-source project, compare it with upstream for changed endpoints and authentication code.

Impact: Knostic described a package that copied Amazon's code and replaced the authentication and API addresses.

Controls:

  • Search the code for hardcoded hosts and for changes to token or API endpoints.
  • Reject packages whose README does not account for the differences.
  • Register risks: R-02, R-03.

Severity: high

Sources: Repackaged Amazon SP-API MCP Sends App Secrets to an Undisclosed IP, Knostic (read ); OWASP MCP Security Cheat Sheet (read ).

C-10: Review every field of each tool definition

Read the descriptions, parameter names, types, defaults, output schemas and annotations of every tool.

Impact: The model reads all of these, and instructions can sit in any of them.

Controls:

  • Look for text that tells the agent to read credentials, call other tools or hide actions from the user.
  • Run a scanner built for tool definitions as a second check; the OWASP cheat sheet names mcp-scan.
  • Register risks: R-23, R-25, R-26.

Severity: high

Sources: OWASP MCP Security Cheat Sheet (read ); When an MCP Tool Asks for Your GitHub Token, Knostic (read ); AI tool poisoning through MCP tool descriptions, CrowdStrike (read ).

C-11: Scan the server's dependencies

Run dependency scanning on the server and review known vulnerabilities and maintenance state.

Impact: A vulnerable dependency runs with the server's permissions.

Controls:

  • Scan lockfiles and container images; track advisories for the servers and SDKs you approve.
  • Prefer servers with a documented update path.
  • Register risks: R-04.

Severity: medium

Sources: OWASP MCP Security Cheat Sheet (read ); Evo ADS MCP Governance Goes GA, Snyk (read ).

C-12: Check the SDK version against current advisories

Find which MCP SDK the server uses and compare it with the advisories published in October 2026.

Impact: SDK flaws affect every server built on the affected versions.

Controls:

  • Compare with the TypeScript SDK advisories (sdk 1.32.0 and server 2.3.0 are the fixed versions named) and the Python SDK advisories (mcp 1.30.0 and 2.2.0).
  • Check the fix needs a setting: GHSA-w4fh-qvv9-3v23 says upgrading alone changes nothing until the audience check is turned on.
  • Register risks: R-08, R-11, R-15, R-21.

Severity: high

Sources: GHSA-rvq5-wwqv-78pq: MCP TypeScript SDK bearer authentication audience (read ); GHSA-w4fh-qvv9-3v23: MCP Python SDK bearer-token audience (read ); GHSA-jm63-cq47-j5jp: MCP TypeScript server SDK cross-client messages (read ); GHSA-46jr-4wx8-v453: MCP TypeScript SDK memory exhaustion (read ).

C-13: Test the server in a sandbox with network capture

Run the candidate server in a disposable environment and record its files touched and hosts contacted.

Impact: Behavior on first run shows whether the server does only what it says.

Controls:

  • Use a container or virtual machine with no real credentials and log outbound connections.
  • Use the MCP Inspector to list tools and review definitions; keep it on a current release.
  • Register risks: R-29, R-22, R-35.

Severity: high

Sources: Local Server Security, modelcontextprotocol.io (read ); MCP Inspector security documentation (read ).

C-14: Review the launch manifest and environment variables

Read the server's manifest or server.json entry and every environment variable it asks for.

Impact: Variables such as NODE_OPTIONS or a registry setting change how the runtime behaves.

Controls:

  • Reject entries with unexplained environment variables or runtime-control variables.
  • Inspector 2.15.0 flags NODE_OPTIONS and npm_config_registry in its server.json preview; use it as a model for your own review.
  • Register risks: R-30, R-03.

Severity: high

Sources: MCP Inspector 2.15.0 release notes (read ); MCP Inspector 2.14.0 release notes (read ).

C-15: Record the decision and pin the approved version

Store the approval with reviewer, date, version and a hash of the tool definitions.

Impact: Without a pin, an approval does not describe tomorrow's server.

Controls:

  • Pin the package version and record the hash of the full tool definition.
  • Do not use registry listings as the approval; key entries by name and version.
  • Register risks: R-05, R-06.

Severity: medium

Sources: OWASP MCP Security Cheat Sheet (read ); MCP Registry v1.8.8 release notes (read ).