MCP Server Security

MCP server security: risk register, checklist and tool comparison

Secure MCP servers by finding every one on developer machines, vetting each before first use, authenticating remote ones with scoped tokens, limiting tool calls, logging them and rehearsing removal. The checklist tracks that work, and the scored comparison puts Snyk (Agent Scan, Evo ADS) first at 77.0 of 100 among 14 tools.

Facts read on .

The short answer

Snyk (Agent Scan, Evo ADS) leads the site ranking at 77.0 of 100. Bay is 10th at 46.0. Snyk (Agent Scan, Evo ADS) is ahead mainly on discovery (8 against 4, worth 10.0 points at weight 25).

Search the risk register and track the checklist

Risk register

Checklist

0 of 42 done.

Progress stays in this browser (local storage) and is never sent anywhere.

The ranking

The full ranking has the same table with re-rank sliders. Each score links to the evidence on the vendor's page.

Site ranking: scores out of 10 per criterion, totals out of 100
RankVendorTotal (of 100)Discovery (weight 25)Vetting before use (weight 20)Runtime control of tool calls (weight 20)Deployment (weight 15)Governance and audit (weight 5)Transparency (weight 10)Proof (weight 5)
1stSnyk (Agent Scan, Evo ADS)77.08968498
2ndCisco71.57868876
3rdHarmonic Security69.08588846
4thKnostic61.06757665
5thBackslash Security58.56765646
6thPillar Security57.06666446
7thLasso Security56.06664747
8thMicrosoft54.58246586
9thNoma Security51.56654536
10thBay46.04466707
11thZenity44.05363537
12thCrowdStrike41.04336547
13thKoi39.04526218
14thSentinelOne (Prompt Security)36.54334346

Who should pick what

With no particular situation, the published ranking applies and Snyk (Agent Scan, Evo ADS) comes first. For a specific situation the weights change, and so can the order:

What would change this ranking

Top pair. Cisco rising from 7 to 10 on discovery (weight 25, so each point moves a total by 2.5) would put Cisco above Snyk (Agent Scan, Evo ADS); the gap is 5.5 points.

Bay's next place. Bay rising from 4 to 7 on discovery (weight 25, so each point moves a total by 2.5) would put Bay above Noma Security; the gap is 5.5 points.

A score changes only when a sourced fact changes, and the weights were fixed before the scores. The method page lists the weights, anchors and rules.

What is MCP server security?

MCP server security is the set of controls that decide which Model Context Protocol servers run, what they can reach and what their tools are allowed to do. It covers local servers that a developer starts from a config file and remote servers reached over HTTP, because both give an AI application the ability to read files, call APIs and run commands.

The protocol leaves much of this to implementers. The MCP specification marks authorization as optional and tells clients to ask for consent before running a local server's startup command, so the work falls to the people who deploy the servers and the clients.

Sources: MCP specification: Authorization (2025-11-25); MCP specification: Security Best Practices (2025-11-25).

Where is the risk register?

The risk register is the searchable table on this page, grouped into six areas: supply chain, authorization, transport and network, tool descriptions and schemas, execution and filesystem, and data exposure and logging. Type a word such as token, npx or log to filter the rows, and each row shows its impact, its controls and its sources.

Every row carries a severity with the rule that sets it, written down on the register's method page. Nothing in a row is a vendor claim unless the row says so.

How does the checklist track progress?

The checklist covers six steps in order: discover, vet, authenticate, constrain, observe and respond. Tick an item and the page counts your progress; the state is stored only in your browser's local storage, so it stays on your machine and clears when you clear site data.

Each step has its own page with the items, the reason for each and the primary source behind it.

Which tools discover MCP servers on developer machines?

Fourteen tools are scored on public evidence, and Snyk (Agent Scan, Evo ADS) ranks first at 77.0. The table below shows every total, and five situation pages re-rank the same evidence for large developer populations, fast inventories, approved catalogs, tool-call blocking and regulated audits.

The comparison covers tools that find and control servers on machines and in developer tools. Gateways sit outside it, and the method page explains why.

How were the sources chosen?

Guides and register rows cite the MCP specification, the OWASP MCP Security Cheat Sheet, GitHub security advisories and the documentation of the clients and cloud services that host servers. Vendor statements about their own products are written as the vendor's, with the page they came from and the date it was read.

Sources: MCP specification: Security Best Practices (2025-11-25); OWASP MCP Security Cheat Sheet.

Latest news, guides and data

Re-rank with your own weights

The ranking above is the published one. Sliders appear here when scripts run; they start at the published weights and show what your weights would give, without changing the published ranking. Restore the published weights.