MCP servers that fail: package name not typosquatting
7 of the 9,159 Model Context Protocol servers where this control could be evaluated fail it — that is 0% of the evaluated corpus on the Canopii Trust Index.
- Servers failing
- 7
- Failure rate
- 0%
- Average score when failing
- 41/100
Why this matters
Names mimicking popular packages are a common malware delivery vector.
How to pass it
Use a clearly distinct, namespaced package name.
Control id supply.not_typosquatting — a guard control, so a confirmed failure caps the server's score at the high ceiling no matter what else passes.
Affected servers
We publish this count, not a list of targets. A confirmed high-severity failure of this control is a directly exploitable weakness. Each affected server's own page carries its result and evidence, so nothing is hidden from someone evaluating a specific server — but we will not publish a ranked list of exploitable systems, which is a different artifact serving a different reader.
Running one of these? The directory and the open-source scanner will tell you where you stand.
This control is one of 29 in the published rubric — see how scoring works or how the ecosystem fails every other control.