How this data is verified

Every entry was sourced via live web search and verified with a real HTTP check — the repo URL directly, and for npm packages, the npm registry API rather than npmjs.com's package page (which blocks automated requests with a 403 regardless of whether the package is real).

Method

1. Web search for the server's official announcement, repo, and npm package.
2. Fetch the repo URL directly and record the HTTP status.
3. Fetch registry.npmjs.org/<package> for npm packages — the real signal of whether a package exists.
4. Where a declared repo URL turned out stale (found during this build: a reference server's documented subpath, and one of the maintainer's own packages), link to the nearest verified real URL instead, noted on that entry's detail page — or the entry is dropped entirely.

Why fewer entries than a rounder number

This directory would rather ship a shorter list where every single entry is real and checked than pad the count with anything unverifiable. More entries get added over time — the bar stays the same as the list grows.

Full provenance log: DATA_PROVENANCE.md in the repo.