mcpreflight / registry changes
Diff of the weekly read-only rescan against the previous week (2026-11-02). 0 added, 0 removed, 0 changed status, out of 35327 endpoints.
Intra-week refresh, not a new weekly diff. The scan on 2026-11-02 falls in the same ISO week as the baseline (2026-11-02), so the baseline was left in place. The numbers above are the status snapshot of the full registry on 2026-11-02; anything that moved between two runs inside the same week is scan jitter, not a week-over-week change. The baseline advances on the first scan of a later ISO week.
Every Monday the whole official registry is re-scanned read only and this page diffs the two weeks. A server appearing here as added was not in the registry the week before. Status changed means its anonymous handshake outcome moved, for example from PASS to AUTH_GATED, which is usually an authentication change rather than an outage. The machine-readable feed with the full arrays is at trust-data/registry-changes.json in the repository.
none this week.
none this week.
none this week.
Method: read-only initialize and tools/list, no tool calls, no credentials, no payments. Auth-gated endpoints are classified, not counted as failures. Tables show up to 200 rows; the JSON feed has everything.
Baseline rule: a diff only advances the stored baseline when the two scan dates fall in different ISO weeks (comparisonKind cross-week). Manual dispatches and retries inside the same week refresh the status snapshot and leave the baseline untouched, so a same-day rerun can never be published as a weekly change.
Cite this as: mcpreflight, MCP Registry Changes, week of 2026-11-02, https://xka0085-byte.github.io/mcpreflight/registry-changes.html . Figures should be attributed to mcpreflight rather than to an anonymous audit.