Sources and method
The catalogue lists AI tools from their public listings: names, versions, dates, counts and addresses. For a tool Stanch reads in full, its servers download the published package or repository at the version listed and read its files. Each tool’s page names the version and the day of every reading.
How we read
- Every request names us: our readers send the User-Agent “Stanch catalogue (+https://stanch.ai)”.
- One request at a time to each source, never sooner after the last one than that source’s pause below.
- When a source asks us to slow down (an answer of 429, or a stated time to wait), we wait as long as it asks; if it asks for more than 15 minutes, we stop reading that source for the run and keep what it gave. We never work around a limit.
- Only public listings, over https. A private repository is never listed.
- We follow each source’s terms of use as we understand them, and read them again before the catalogue server’s first run and whenever a source changes them.
- We keep no person’s name or e-mail address from a listing.
Each source
| Source | What we read | Pause between two requests | What its terms allow, as we read them | What this site shows |
|---|---|---|---|---|
| The official MCP registry | Each server’s listing through the registry’s public API: name, version, title, description, repository, packages, icons, status and dates. | 250 ms | A public, community-run list; its read API needs no account, and its documentation describes catalogues that copy the list on a schedule. | Facts, the link, and the listing’s own short description, marked as the publisher’s words from the registry. |
| npm | The registry’s search for the MCP keywords, and each listed package’s latest version. | 1 s for search; 200 ms for a package, asked only if it changed | A public, documented API that every installer reads; its terms ask that the service is not burdened and its limits are not worked around. | Facts and the link only: name, version, dates and publisher scope. No description. |
| PyPI | The JSON of packages the MCP registry names: the latest version. | 200 ms, asked only if it changed | A public, documented JSON API; its guidance asks clients to name themselves, use conditional requests and not send many at once. | Facts and the link only. No description. |
| GitHub | Public repositories with skill files or plugin manifests, through the REST API: search, each repository’s record, the commit its branch names and the names of its files. For a full reading, the repository’s archive at that commit. | Within GitHub’s stated limits: 2.1 s for search, 6.1 s for code search, 0.75 s otherwise | Its API terms allow use within the rate limits, without multiplying tokens, and restrict what collected information is used for. | Facts and the link only: name, repository, folder, commit and dates. No description. |
| Open VSX | Its documented search by category and by text: each extension’s name, version, date and downloads. | 1 s | The Eclipse Foundation’s vendor-neutral registry, made for any editor or tool, under the Foundation’s terms of use; each extension keeps its own licence. | Facts and the link only. No description. |
| VS Code Marketplace | Nothing by default. Our reader is off unless a run names it, and no package is ever fetched from it. | 2 s, when a run names it | Its terms license its offerings for use with the vendor’s own products, and do not plainly allow another product’s automated reading. | Nothing. If its listings are ever shown: facts and the link only. |
| Browser extension stores | Nothing. | - | Most stores offer no public listing API for other parties and do not allow automated reading of their pages. | Nothing. |
What each page shows
- A tool’s name, version, publisher and dates as its registry records them: facts, used to identify the tool.
- A picture only from the tool’s own listing at its publisher’s own address, or the picture of its publisher’s GitHub organisation. Never a person’s picture.
- A listing’s own description only where we read that source’s terms as allowing it (so far, only the official MCP registry), marked as the publisher’s words, with a link to its source. Our reading of each source’s terms is being checked by a lawyer.
- Stanch’s reading: the version or commit read, the day, what was found in plain words, and how much of the tool was read.
What a reading is, and is not
- A reading is what Stanch’s checks found in one version, on one day. A new version is a new tool until it is read.
- Not scanned yet means Stanch has not read it. Listed only means Stanch can read its listing but not its code. Neither one is a clean result.
- Nothing found means our checks found nothing in what they read. Not a guarantee: a tool with nothing found can still do harm.
Something wrong?
Publishers can ask for a correction, a new reading or a removal, without an account. Corrections and removal