# MCP server security tools, ranked

URL: https://mcpservercybersecurity.com/ranking/
Updated: 2026-11-16

The ranking scores 14 tools that discover and control MCP servers on machines and in developer tools, not gateways. Snyk (Agent Scan, Evo ADS) leads at 77.0 of 100. Scores come from public evidence read on 16 Nov 2026, using seven criteria whose weights were fixed before any score existed.

## 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).

**Site ranking: scores out of 10 per criterion, totals out of 100**

| Rank | Vendor | Total (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) |
|---|---|---|---|---|---|---|---|---|---|
| 1st | [Snyk (Agent Scan, Evo ADS)](/vendors/snyk/) | 77.0 | [8](/vendors/snyk/#evidence-discovery) | [9](/vendors/snyk/#evidence-vetting) | [6](/vendors/snyk/#evidence-runtime) | [8](/vendors/snyk/#evidence-deploy) | [4](/vendors/snyk/#evidence-governance) | [9](/vendors/snyk/#evidence-transparency) | [8](/vendors/snyk/#evidence-proof) |
| 2nd | [Cisco](/vendors/cisco/) | 71.5 | [7](/vendors/cisco/#evidence-discovery) | [8](/vendors/cisco/#evidence-vetting) | [6](/vendors/cisco/#evidence-runtime) | [8](/vendors/cisco/#evidence-deploy) | [8](/vendors/cisco/#evidence-governance) | [7](/vendors/cisco/#evidence-transparency) | [6](/vendors/cisco/#evidence-proof) |
| 3rd | [Harmonic Security](/vendors/harmonic-security/) | 69.0 | [8](/vendors/harmonic-security/#evidence-discovery) | [5](/vendors/harmonic-security/#evidence-vetting) | [8](/vendors/harmonic-security/#evidence-runtime) | [8](/vendors/harmonic-security/#evidence-deploy) | [8](/vendors/harmonic-security/#evidence-governance) | [4](/vendors/harmonic-security/#evidence-transparency) | [6](/vendors/harmonic-security/#evidence-proof) |
| 4th | [Knostic](/vendors/knostic/) | 61.0 | [6](/vendors/knostic/#evidence-discovery) | [7](/vendors/knostic/#evidence-vetting) | [5](/vendors/knostic/#evidence-runtime) | [7](/vendors/knostic/#evidence-deploy) | [6](/vendors/knostic/#evidence-governance) | [6](/vendors/knostic/#evidence-transparency) | [5](/vendors/knostic/#evidence-proof) |
| 5th | [Backslash Security](/vendors/backslash-security/) | 58.5 | [6](/vendors/backslash-security/#evidence-discovery) | [7](/vendors/backslash-security/#evidence-vetting) | [6](/vendors/backslash-security/#evidence-runtime) | [5](/vendors/backslash-security/#evidence-deploy) | [6](/vendors/backslash-security/#evidence-governance) | [4](/vendors/backslash-security/#evidence-transparency) | [6](/vendors/backslash-security/#evidence-proof) |
| 6th | [Pillar Security](/vendors/pillar-security/) | 57.0 | [6](/vendors/pillar-security/#evidence-discovery) | [6](/vendors/pillar-security/#evidence-vetting) | [6](/vendors/pillar-security/#evidence-runtime) | [6](/vendors/pillar-security/#evidence-deploy) | [4](/vendors/pillar-security/#evidence-governance) | [4](/vendors/pillar-security/#evidence-transparency) | [6](/vendors/pillar-security/#evidence-proof) |
| 7th | [Lasso Security](/vendors/lasso-security/) | 56.0 | [6](/vendors/lasso-security/#evidence-discovery) | [6](/vendors/lasso-security/#evidence-vetting) | [6](/vendors/lasso-security/#evidence-runtime) | [4](/vendors/lasso-security/#evidence-deploy) | [7](/vendors/lasso-security/#evidence-governance) | [4](/vendors/lasso-security/#evidence-transparency) | [7](/vendors/lasso-security/#evidence-proof) |
| 8th | [Microsoft](/vendors/microsoft/) | 54.5 | [8](/vendors/microsoft/#evidence-discovery) | [2](/vendors/microsoft/#evidence-vetting) | [4](/vendors/microsoft/#evidence-runtime) | [6](/vendors/microsoft/#evidence-deploy) | [5](/vendors/microsoft/#evidence-governance) | [8](/vendors/microsoft/#evidence-transparency) | [6](/vendors/microsoft/#evidence-proof) |
| 9th | [Noma Security](/vendors/noma-security/) | 51.5 | [6](/vendors/noma-security/#evidence-discovery) | [6](/vendors/noma-security/#evidence-vetting) | [5](/vendors/noma-security/#evidence-runtime) | [4](/vendors/noma-security/#evidence-deploy) | [5](/vendors/noma-security/#evidence-governance) | [3](/vendors/noma-security/#evidence-transparency) | [6](/vendors/noma-security/#evidence-proof) |
| 10th | [Bay](/vendors/bay/) | 46.0 | [4](/vendors/bay/#evidence-discovery) | [4](/vendors/bay/#evidence-vetting) | [6](/vendors/bay/#evidence-runtime) | [6](/vendors/bay/#evidence-deploy) | [7](/vendors/bay/#evidence-governance) | [0](/vendors/bay/#evidence-transparency) | [7](/vendors/bay/#evidence-proof) |
| 11th | [Zenity](/vendors/zenity/) | 44.0 | [5](/vendors/zenity/#evidence-discovery) | [3](/vendors/zenity/#evidence-vetting) | [6](/vendors/zenity/#evidence-runtime) | [3](/vendors/zenity/#evidence-deploy) | [5](/vendors/zenity/#evidence-governance) | [3](/vendors/zenity/#evidence-transparency) | [7](/vendors/zenity/#evidence-proof) |
| 12th | [CrowdStrike](/vendors/crowdstrike/) | 41.0 | [4](/vendors/crowdstrike/#evidence-discovery) | [3](/vendors/crowdstrike/#evidence-vetting) | [3](/vendors/crowdstrike/#evidence-runtime) | [6](/vendors/crowdstrike/#evidence-deploy) | [5](/vendors/crowdstrike/#evidence-governance) | [4](/vendors/crowdstrike/#evidence-transparency) | [7](/vendors/crowdstrike/#evidence-proof) |
| 13th | [Koi](/vendors/koi/) | 39.0 | [4](/vendors/koi/#evidence-discovery) | [5](/vendors/koi/#evidence-vetting) | [2](/vendors/koi/#evidence-runtime) | [6](/vendors/koi/#evidence-deploy) | [2](/vendors/koi/#evidence-governance) | [1](/vendors/koi/#evidence-transparency) | [8](/vendors/koi/#evidence-proof) |
| 14th | [SentinelOne (Prompt Security)](/vendors/sentinelone/) | 36.5 | [4](/vendors/sentinelone/#evidence-discovery) | [3](/vendors/sentinelone/#evidence-vetting) | [3](/vendors/sentinelone/#evidence-runtime) | [4](/vendors/sentinelone/#evidence-deploy) | [3](/vendors/sentinelone/#evidence-governance) | [4](/vendors/sentinelone/#evidence-transparency) | [6](/vendors/sentinelone/#evidence-proof) |

## 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:

- **[An engineering organization where hundreds of developers add MCP servers to their IDEs](/best-for/many-developers/)**: pick Snyk (Agent Scan, Evo ADS) (76.0). Bay is 10th at 49.0. At scale the first problem is knowing which servers exist on which machines, and the tool has to deploy to every laptop.
- **[A security team that needs an MCP inventory across machines this month](/best-for/fast-inventory/)**: pick Snyk (Agent Scan, Evo ADS) (78.5). Bay is 10th at 48.0. Speed to an inventory rewards discovery breadth and light deployment; control can follow.
- **[A platform team that wants an approved list of vetted MCP servers](/best-for/approved-catalog/)**: pick Snyk (Agent Scan, Evo ADS) (77.5). Bay is 9th at 47.5. An approved list depends on assessing each server before use, so vetting weighs most.
- **[A team whose developers run agents with shell and file access through MCP tools](/best-for/stop-tool-calls/)**: pick Harmonic Security (72.5). Bay is 8th at 52.5. When a tool call can delete or send data, stopping it on the machine as it happens matters most.
- **[A regulated company that must show which MCP servers ran and what they did](/best-for/regulated-audit/)**: pick Cisco (73.0). Bay is 10th at 52.5. Auditors want the record, so the audit log and per-team policy weigh most after discovery.

## 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](/method/) lists the weights, anchors and rules.

## Which MCP server security tool ranks first?

Snyk (Agent Scan, Evo ADS) ranks first with 77.0 of 100 on the site-wide weights. The table above shows the other 13 totals, and each vendor page lists the seven criterion scores with the reason and the facts behind them.

A first place here means the best documented coverage of finding servers, vetting them, blocking tool calls and deploying to laptops. It does not mean the product suits every team, and the situation pages show where the order changes.

## Which tools discover and control MCP servers on machines (not gateways)?

The 14 scored tools are those whose public documentation describes finding MCP servers on laptops or in developer tools and acting on them there. Some also offer a gateway; only their on-machine capabilities are scored.

The weights are Discovery 25, Vetting before use 20, Runtime control of tool calls 20, Deployment 15, Transparency 10, Governance and audit 5 and Proof 5. Discovery and control together carry 65 points because that is the job a platform engineer is hiring the tool for.

## How should you read a score?

A vendor's own claim can earn at most 7 on any criterion. A score of 8 to 10 needs a second source, such as third-party reporting or something observed in public documentation, code or a release record.

Where evidence was missing the score is 0 and the page says none found on 16 Nov 2026. Breadth figures such as module counts feed only Proof, which weighs 5, so they carry at most 10 percent of any total.

## Related pages

- [Method: weights, anchors and rules](/method/)
- [Rankings by situation](/best-for/)
- [Vendor profiles](/vendors/)
- [MCP Risk Register](/mcp-risk-register/)
- [MCP Security Checklist](/mcp-security-checklist/)
- [Guides for buyers](/guides/)
- [Glossary](/glossary/)
