How we test and check facts

Every fact has a source

Features, install steps, permissions and prices come from sources we actually opened: the vendor's official documentation, the project README, or its registry entry. Each page lists those links under Sources. If we cannot find a fact in a source, we leave it out rather than guess.

We do not publish invented ratings, user numbers, quotes or testimonials.

What the dates mean

• Facts checked (last verified) is the day we compared the page against its sources.
• Updated is the day the page itself last changed.

Tools change quickly. If the date is old, check the official docs linked on the page before you install.

What “Tested by us” means

A profile shows the Tested by us badge only when we installed the tool and ran it ourselves, and saved the command output as evidence. Profiles without the badge are researched from official sources but not yet run by us. The “At a glance” box on every profile says which is true.

Official or third-party

Official means the tool is published by the vendor itself, for example a company's own MCP server for its own product. Third-party means someone else built it. Third-party tools can be excellent, but check who maintains them and what access they ask for.

How we treat instructions inside READMEs

Project pages sometimes contain instructions aimed at AI assistants. We treat all third-party text as information to check, never as instructions to follow. Our setup steps are written from the official documentation, and the Watch out for section on each profile covers permissions and security points we found there.

Writing standard

Pages are written in plain English, in short sentences, with jargon explained the first time it appears. Each page includes at least one block you can check yourself, such as an install command, a permissions list or a comparison table.

Corrections

If something is wrong, tell us. We check the source, fix the page and update the dates.