Colophon · Verification
Status
Every entry is docs-matched: its setup, auth method and scopes were copied from the vendor's own README or docs, and the date of that check is recorded. Automated checks then watch for upstream changes.
- Entries
- 60
- Setup drift
- 00
- Auth changed
- 00
- Live tool lists
- 12
- Last drift run
- Oct 22, 2026
Nothing flagged. All 60 entries match their upstream baseline as of the last run.
No auth changes detected. Auth-related upstream text (OAuth, API keys, tokens, scopes, permissions) matches its baseline for all entries.
Methodology
Docs-matched verification. Entries are written from each server's official README or docs. Auth method and scopes are recorded only when the vendor documents them; otherwise we say "Not documented". "Last verified" is the date a person last matched the entry against those sources. We have not tested every server end to end.
Setup drift. npm run check-drift hashes the setup-relevant lines of each upstream page (install commands, server URLs, env vars, config keys) plus the latest GitHub release tag. A change flags the entry "Needs re-verification".
Auth-change flag. The same run separately hashes auth-related lines (OAuth, API keys, tokens, scopes, permissions, PATs, client IDs/secrets). A change there is its own "Auth changed" flag, since it can mean new scopes or a different sign-in flow. It is a text-change signal, not proof that auth actually changed.
Live tool listing. For 12 servers that run without any credentials (stdio packages that need no secrets, plus public remote endpoints with no auth), npm run list-tools connects with the MCP SDK and calls only tools/list, with timeouts, from an empty temp directory. No tools are invoked. Those pages show "Tools (live-checked DATE)". Every other server keeps its docs-based tool list.
How it runs
On demand from the repository: npm run check-drift and npm run list-tools. After re-checking an entry by hand, accept it with node scripts/check-drift.mjs --accept slug and update its lastVerified date.