1. Source check
We record the original repository, documentation, or publisher page and prefer first-party sources. Community sources are labeled separately.
Our methodology
How a resource earns its place.
We separate source evidence, metadata quality, installation checks, and editorial recommendations. This prevents one positive signal from being mistaken for a complete safety review.
2. Metadata check
We check the resource name, category, description, license, supported platforms, installation path, and update information. Missing information stays visible.
3. Permission review
For tools such as MCP servers, we identify filesystem access, network access, secrets, external writes, and other meaningful permissions.
4. Installation test
A resource is not marked Verified until the required installation and configuration checks have been performed by a human reviewer.
5. Editorial judgment
We add practical guidance: who the resource fits, where it may fail, what to watch for, and which alternatives are worth considering.
6. Maintenance
Source checks, metadata updates, and installation tests have separate timestamps so outdated verification does not look current.
Status labels
Official source means the link points to a first-party source. Source checked means the source and basic metadata were reviewed. Install test needed means it has not yet completed our human installation check. Verified is reserved for resources that passed the required review scope.