MCP Server Security

MCP security checklist: discover

Seven steps find every MCP client and server on machines before anything else: list clients, collect config files, record launch commands, turn on endpoint discovery, find network listeners, assign owners and diff against the catalog. Each step names controls and sources, with priority set by the written rule, read on 16 Nov 2026.

Facts read on .

What this stage covers

Find every MCP client and server on machines and in repositories. There are 7 steps here (C-01 to C-07), each a concrete action an engineer can tick.

Sources: Local Server Security, modelcontextprotocol.io; Connect Claude Code to tools via MCP, Claude Code docs; MCP Security Best Practices, 2026-07-28 revision.

Steps in order

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

Sources: Local Server Security, modelcontextprotocol.io; Connect Claude Code to tools via MCP, Claude Code docs; MCP Security Best Practices, 2026-07-28 revision; What's new in Microsoft Defender for Endpoint.

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: Local Server Security, modelcontextprotocol.io; Connect Claude Code to tools via MCP, Claude Code docs; MCP Security Best Practices, 2026-07-28 revision; What's new in Microsoft Defender for Endpoint.

Discover: 7 items

C-01: List every MCP client in use

Write down each application that can load MCP servers: IDEs, desktop AI apps and command-line agents, with versions.

Impact: A server cannot be found if the client that loads it is unknown.

Controls:

  • Survey developers and read software inventory for IDEs, desktop AI apps and agent command-line tools.
  • Record where each client keeps its MCP configuration (user, project and managed levels).
  • Register risks: R-07.

Severity: high

Sources: Local Server Security, modelcontextprotocol.io (read ); Connect Claude Code to tools via MCP, Claude Code docs (read ).

C-02: Collect MCP configuration files from machines

Gather the config files that list servers, including project files that arrive with repositories.

Impact: Config files hold the launch commands that decide what code runs.

Controls:

  • Read user-level and project-level files such as .mcp.json and client settings files, and the managed settings you control.
  • Store the collected result with machine, user and date.
  • Register risks: R-07, R-33.

Severity: high

Sources: Connect Claude Code to tools via MCP, Claude Code docs (read ); MCP Security Best Practices, 2026-07-28 revision (read ).

C-03: Record how each server is launched

For every server note the command, package name, version, publisher and any environment variables it receives.

Impact: The launch command is what the machine executes; a changed package name or flag is the first sign of a problem.

Controls:

  • Capture the full command without truncation, including npx or other launcher flags.
  • Note which environment variables and credentials the server is given.
  • Register risks: R-01, R-03, R-07.

Severity: high

Sources: MCP Security Best Practices, 2026-07-28 revision (read ); Local Server Security, modelcontextprotocol.io (read ).

C-04: Turn on endpoint discovery of configured servers

Use an endpoint tool that reports MCP servers configured on managed machines, so the inventory does not depend on surveys.

Impact: Manual surveys go stale; machine-reported inventory shows servers as they are added.

Controls:

  • Microsoft documents local AI agent discovery, generally available on Windows and macOS in October 2026, that reports each agent's configured MCP servers in Defender for Endpoint.
  • Snyk says Evo ADS MCP Governance discovers MCP servers across the estate, and Cisco's DefenseClaw 1.0.0 notes list a per-item MCP inventory; compare coverage against your clients before choosing.
  • Register risks: R-07.

Severity: high

Sources: What's new in Microsoft Defender for Endpoint (read ); Evo ADS MCP Governance Goes GA, Snyk (read ); DefenseClaw 1.0.0 release notes, Cisco (read ).

C-05: Find remote and HTTP MCP endpoints on your network

List MCP servers that listen on a port or are hosted for team use, and who can reach them.

Impact: A server listening on all interfaces, or without authentication, serves its tools to the network.

Controls:

  • Check for MCP servers bound to 0.0.0.0 on developer subnets and for hosted servers in cloud accounts.
  • Record each endpoint's authentication method.
  • Register risks: R-09, R-17.

Severity: high

Sources: MCP Streamable HTTP transport, 2026-07-28 revision (read ); OWASP MCP Security Cheat Sheet (read ).

C-06: Assign an owner and review date to each server

Give every server in the inventory a named owner, a purpose and a date by which it is re-reviewed.

Impact: Servers without an owner are never patched or removed.

Controls:

  • Keep owner, purpose, version and next review in the catalog record.
  • Remove servers whose owner cannot be found.
  • Register risks: R-07.

Severity: high

Sources: Local Server Security, modelcontextprotocol.io (read ); Evo ADS MCP Governance Goes GA, Snyk (read ).

C-07: Compare the inventory with the approved catalog on a schedule

Diff what is installed against what is approved and report the difference to the owners.

Impact: New and unapproved servers appear continuously; drift left unchecked becomes the norm.

Controls:

  • Run the comparison weekly and report new servers by machine and team.
  • Track servers that changed version since approval.
  • Register risks: R-07, R-05.

Severity: high

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