Registry Coverage
Distinguishing passive indexing from trust signals that came from actual live interaction, certification review, or ongoing monitoring.
How the public metrics work
Discovered in the ecosystem
Servers found through npm, GitHub, docs sites, and community references. Useful for coverage, but not proof of runtime behavior.
Actually contacted and exercised
CraftedTrust connected to the target and generated evidence from live interaction, not just metadata.
Reviewed for public trust signaling
Publisher completed assisted review and certification workflows, earning public certification status and reports.
Tracked for drift over time
Recurring re-scan and score-change monitoring. The strongest ongoing signal in the public registry.
Why live verification matters
How to improve coverage quality
- Request verification when a server is important to your workflow but only passively indexed
- Sponsor a scan for ecosystems or tool categories you want prioritized
- Encourage publishers to move from indexing into certification and monitoring
- Use badge embeds and profile traffic as prioritization signals for recurring work
Take action
CraftedTrust is an input to approval, not a substitute for it. Use buyer diligence when your team needs help interpreting score, scan depth, and public research in a real approval workflow.