Methodology

Where listings come from

Kitbay collects servers and skills from the official MCP Registry, from GitHub (repositories and SKILL.md files), and from the npm and PyPI package registries. Other directories are used only as leads: we take a project's name and repository link, never their descriptions, ratings or screenshots.

Noise is filtered out and kept in the database with a reason: test and demo projects, unchanged forks, mirrors, link lists, bulk-generated micro-tools, and anything unsafe.

How facts are checked

Every stored fact has a source URL and the date it was checked. Sources are the project's own repository, files and package pages, its homepage, and the tool vendor's own documentation.

Researched listings get a summary written in our own words from those sources, never copied from a README. Facts we can't confirm are shown as “not stated in its documentation”, never guessed. Unknown is a valid answer.

What “official” means

A listing is official only when the tool's vendor or its developers publish it: in their own GitHub organisation, on their package account or on their website, or when the vendor's own pages link to it. Each Official badge links to that evidence. Where a vendor publishes something but says it doesn't support it, the listing says so.

How listings are sorted

Tool, category and client pages show official listings first, then sort by a score with four parts: evidence completeness (how many key facts are confirmed, up to 40 points), activity (recent commits and releases, archived projects last, up to 25), documentation (a usable README or vendor docs, up to 15) and popularity (GitHub stars, plus package downloads as a bonus when available, up to 20). Missing download data is never a penalty, and sudden spikes are capped and flagged for review.

The score only orders a list. It isn't a rating or a recommendation, and you can re-sort any table by downloads, stars, last update or name.

Which pages search engines see

Every genuine listing can be browsed, but a page is offered to search engines only when it meets clear rules: an original summary of about 60 words or more, at least two capabilities with evidence, a known connection type (servers) or known files (skills), install instructions from the project's own source, a known licence, and recent activity unless it's official or the only option for its tool. Engineering listings are never indexed here; they belong to Tresca.

Indexing grows gradually, with a cap of 2300 indexable pages that rises as the site earns trust.

Copies and safety

When the same skill is copied into many repositories, Kitbay shows one listing and groups the copies under it. Identical copies redirect to the original; changed copies are labelled with how much of the text they share.

Kitbay scans repositories for known malware patterns, such as look-alike repositories whose links all point to a downloadable archive, and hides those listings with the evidence recorded. Any MCP server or skill can run code and act on your data, so always review the source before installing.