github
Atlas/Guides/Trust/Trust, provenance, and what to install
Trust·All levels·8 min read

Trust, provenance, and what to install

How MCP Atlas surfaces provenance, why we don't rank, and how to read source signals when picking a server.

Atlas doesn't tell you which server is best. It tells you where every server came from, and lets you decide. This guide explains how to read the provenance trail on every card.

Why we don't rank

Ranking implies a single best answer. For most MCP categories there isn't one — the right database server depends on which database you're running, the right note-taking server depends on which app you use. A score would flatten that into something misleading.

What the dots mean

Each card shows a row of source dots: official, smithery, glama, pulsemcp, community. A filled dot means the server appears in that source. More dots is a stronger signal that the server is real and maintained, but it isn't a quality score — abandoned servers can be widely indexed.

How to combine signals

  • Official registry presence — strongest signal of spec compliance.
  • Recent commits — signal of active maintenance.
  • Multiple marketplace listings — signal of broad availability.
  • Read the actual source — the only signal that's always reliable.