# How MCP security tools are scored

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

Every vendor followed one research plan on 16 Nov 2026, producing 1,469 facts in 32 vendor files, 733 of them in this site's 14. The 1,273 facts with a quote were each checked against their pages. One scorer then scored the 14 vendors blind, and a second reviewer checked the result blind. The weights were committed first.

## The weights

The weights were fixed on 2026-11-16, before any score existed, and have not changed since.

**Criteria and weights (out of 100)**

| Criterion | What it measures | Weight |
|---|---|---|
| Discovery | Finding the MCP servers configured on machines and in developer tools (desktop AI apps, IDEs, command-line agents), with the servers, tools and clients named, as documented | 25 |
| Vetting before use | Assessing a server before it runs: scanning code, tool descriptions and permissions, reputation or provenance, an approved list or registry, as documented | 20 |
| Runtime control of tool calls | Allowing, blocking or requiring approval for an MCP tool call on the machine as it happens, with arguments inspected, as documented | 20 |
| Deployment | How it deploys on developer machines (agentless, MDM script, endpoint agent, IDE extension, command-line scanner), operating systems, time to deploy | 15 |
| Governance and audit | Policy per team or server, an audit log of servers and tool calls, export to SIEM | 5 |
| Transparency | Public documentation readable without sign-in, a published price, published research or open-source code | 10 |
| Proof | Named customers, funding, independent analyst coverage | 5 |

## Weights by situation

**Weights used for each situation view**

| Situation | Discovery | Vetting before use | Runtime control of tool calls | Deployment | Governance and audit | Transparency | Proof |
|---|---|---|---|---|---|---|---|
| [An engineering organization where hundreds of developers add MCP servers to their IDEs](/best-for/many-developers/) | 30 | 15 | 20 | 20 | 5 | 5 | 5 |
| [A security team that needs an MCP inventory across machines this month](/best-for/fast-inventory/) | 40 | 10 | 5 | 30 | 5 | 5 | 5 |
| [A platform team that wants an approved list of vetted MCP servers](/best-for/approved-catalog/) | 15 | 40 | 15 | 10 | 10 | 5 | 5 |
| [A team whose developers run agents with shell and file access through MCP tools](/best-for/stop-tool-calls/) | 15 | 15 | 40 | 10 | 10 | 5 | 5 |
| [A regulated company that must show which MCP servers ran and what they did](/best-for/regulated-audit/) | 25 | 15 | 15 | 5 | 30 | 5 | 5 |

## Score anchors

- **0**: none found on the read date
- **1-3**: mentioned, partial, or limited to one surface, one layer or one action type
- **4-6**: documented and working, with gaps the documentation shows
- **7**: the most a vendor claim or vendor documentation alone can earn: detailed, specific, covering the whole criterion
- **8-10**: detailed and confirmed by a second source (third-party write-up, or observed directly in public documentation, code, a marketplace listing or a release record)

## Rules

- Every vendor is scored 0 to 10 on every criterion, whole numbers, from the evidence file only, by a scorer that works from coded packets with every vendor name removed.
- A vendor claim scores at most 7 until a second source confirms it (kind third-party or observed).
- None found scores 0 and is written "none found on the read date".
- Breadth facts (module counts, integration counts, headcount, funding) inform Proof only, which weighs 5, so they carry at most 10 percent of any ranking.
- The total is the weighted sum of the scores divided by 10 (0 to 100 scale, published to one decimal).
- Equal totals print as a joint rank (for example joint 2nd); inside a joint rank vendors are listed alphabetically for display only.
- Once the first score exists, no weight and no criterion changes. A score changes only when a sourced fact changes, logged with the fact.

## How are MCP security tools scored?

Each vendor is scored from 0 to 10 on seven criteria, and the total is the weighted sum divided by 10, shown on a 0 to 100 scale to one decimal. Scores are whole numbers and come from the vendor's evidence file only.

The criteria and 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. They were written and committed on 16 Nov 2026 before any evidence file or score existed, and none has changed since the first score.

## What is the evidence base?

A single research plan was applied to every vendor on 16 Nov 2026. It produced 1,469 facts across 32 vendor files, 733 of them in this site's 14 files. Of the 1,469, 196 are none-found records with no quote, and the other 1,273 were each quote checked against their pages. Each fact stores the claim, the quoted passage, the source URL, the read date and a kind: vendor, third-party, observed or none found.

A quote check compared every stored quote with the page it came from. A fact whose quote could not be found on the page was removed or corrected before scoring.

## How does blind scoring work?

One scorer read each evidence file with the vendor shown under a letter code rather than a name, and scored it against the anchors. A second reviewer then checked every score, also blind, and any disagreement was settled by the cited facts.

The anchors are fixed: 0 for none found, 1 to 3 for a mention or a partial, single-surface capability, 4 to 6 for documented and working with visible gaps, 7 as the most a vendor claim alone can earn, and 8 to 10 when a second source confirms the claim.

## Why are gateways out of scope?

Gateways are out of scope because the reader's job here is to find and control the servers installed on machines, and a gateway only sees traffic routed through it. A server started from a config file on a laptop never touches a gateway unless someone forces it to.

Where a vendor ships a gateway next to an on-machine component, only the on-machine capability is scored. Ranking gateways is a separate comparison that this site does not publish.

## How are scores corrected?

A score changes only when a sourced fact changes, and the change is logged with the fact on the changelog the method page prints. Weights and criteria do not change after the first score.

To report an error, write to editor@mcpservercybersecurity.com with the page and the source that contradicts it. The corrections page explains how reports are handled.

## Changelog

- 2026-11-16: weights and criteria fixed.
- 2026-11-16: evidence read for every vendor by one research plan.
- 2026-11-16: scores published (blind: one scorer, then one blind reviewer).
- 2026-11-16: this site built from the committed scores.

## Related pages

- [The ranking these weights produce](/ranking/)
- [Vendor profiles with evidence per score](/vendors/)
- [Editorial policy](/editorial-policy/)
- [Corrections](/corrections/)
- [Glossary](/glossary/)
- [MCP Risk Register](/mcp-risk-register/)
- [MCP Security Checklist](/mcp-security-checklist/)
