How to tell if an MCP server is safe
What are the real security risks of an MCP server?
The named ones: tool-poisoning / prompt-injection via tool descriptions the model sees but you don't; rug-pulls (a server silently changing tool behavior after you approve it); single-maintainer / supply-chain risk; and typosquats (near-identical names). None of these show up in a star count.
How does tashan help judge MCP safety?
Every capability page shows the bus factor (real contributor count), an archived/deprecated flag, the maintainer and license, and a plain-language read. It's a maintenance/adoption read, not a full audit — but it's the fast first filter a store's install counter can't give you. Read the methodology.
FAQ
Are MCP servers safe to run?
They're as safe as any tool you install — judge the maintainer, recency, and permission surface. Prefer official or well-maintained servers; be cautious with single-maintainer, archived, or typosquat-looking ones.
Can an MCP server steal my data?
A malicious one with file/network access could, which is why the permission surface and maintainer trust matter. tashan flags single-maintainer and archived servers as elevated risk.
This article and every score it links to are free, no account. Check your own config free too. Pro adds the series behind each row, and names a replacement when one is dying.
- The whole series behind any row, back to the first day we measured it
- The replacement, named — not just the news that something died
tashan doctorover your own config, on your own machine
Start a 7-day trial › Everything measured on this page stays free.