# Best MCP security tool for an approved server catalog

URL: https://mcpservercybersecurity.com/best-for/approved-catalog/
Updated: 2026-11-16

For a platform team that wants an approved list of vetted MCP servers, Snyk (Agent Scan, Evo ADS) ranks first in this view. Vetting before use weighs 40, because an approved list is only as good as the assessment behind each entry, and an enforced list needs runtime control too.

## The short answer

Snyk (Agent Scan, Evo ADS) leads the view "A platform team that wants an approved list of vetted MCP servers" at 77.5 of 100. Bay is 9th at 47.5. Snyk (Agent Scan, Evo ADS) is ahead mainly on vetting before use (9 against 4, worth 20.0 points at weight 40).

## Why these weights

An approved list depends on assessing each server before use, so vetting weighs most.

**Weights used in this view**

| Discovery | Vetting before use | Runtime control of tool calls | Deployment | Governance and audit | Transparency | Proof |
|---|---|---|---|---|---|---|
| 15 | 40 | 15 | 10 | 10 | 5 | 5 |

**A platform team that wants an approved list of vetted MCP servers: scores out of 10 per criterion, totals out of 100**

| Rank | Vendor | Total (of 100) | Discovery (weight 15) | Vetting before use (weight 40) | Runtime control of tool calls (weight 15) | Deployment (weight 10) | Governance and audit (weight 10) | Transparency (weight 5) | Proof (weight 5) |
|---|---|---|---|---|---|---|---|---|---|
| 1st | [Snyk (Agent Scan, Evo ADS)](/vendors/snyk/) | 77.5 | [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/) | 74.0 | [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/) | 65.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/) | 63.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/) | 62.0 | [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 | [Lasso Security](/vendors/lasso-security/) | 58.5 | [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) |
| 7th | [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) |
| 8th | [Noma Security](/vendors/noma-security/) | 54.0 | [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) |
| 9th | [Bay](/vendors/bay/) | 47.5 | [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) |
| 10th | [Microsoft](/vendors/microsoft/) | 44.0 | [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) |
| joint 11th | [Koi](/vendors/koi/) | 41.5 | [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) |
| joint 11th | [Zenity](/vendors/zenity/) | 41.5 | [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) |
| 13th | [CrowdStrike](/vendors/crowdstrike/) | 39.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) |
| 14th | [SentinelOne (Prompt Security)](/vendors/sentinelone/) | 34.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) |

## What would change this ranking

**Top pair.** Cisco rising from 8 to 9 on vetting before use (weight 40, so each point moves a total by 4.0) would put Cisco above Snyk (Agent Scan, Evo ADS); the gap is 3.5 points.

**Bay's next place.** Bay rising from 4 to 6 on vetting before use (weight 40, so each point moves a total by 4.0) would put Bay above Noma Security; the gap is 6.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 tool suits an approved catalog of MCP servers?

Snyk (Agent Scan, Evo ADS) ranks first in this view. An approved list depends on assessing each server before use, so Vetting weighs 40, with Discovery 15, Runtime 15, Deployment 10, Governance 10, and Transparency and Proof 5 each.

Vetting scores reward scanning code, tool descriptions and permissions, plus provenance signals and an enforced list. A scan with no way to enforce the verdict scores lower than one that blocks an unlisted server.

## What does a catalog need beyond a scan?

A catalog needs a named approver, a record of what was reviewed and a trigger for review when a server changes. The MCP Registry verifies who owns a namespace but leaves security scanning of server code to others, so the review stays with you.

The building-an-approved-catalog guide covers the approval workflow without reference to any product.

## What would change this view?

Documented handling of servers that are not in a vendor's catalog, such as locally written stdio servers, would raise Vetting scores. So would an enforced allowlist that ships enabled rather than empty.

## Related pages

- [All situations](/best-for/)
- [A security team that needs an MCP inventory across machines this month](/best-for/fast-inventory/)
- [A team whose developers run agents with shell and file access through MCP tools](/best-for/stop-tool-calls/)
- [Overall ranking](/ranking/)
- [Method and weights](/method/)
- [Vendor profiles](/vendors/)
