If you resolve MCP servers from the registry, roughly one entry in eight is wrong about something the registry never checks.

01REGISTRYThe MCP registry has been measured three times in ten days — and it never re-checks anything it published

Three unrelated parties probed the official MCP registry, and the practical finding is that registry presence is no evidence of availability.

Three measurements, three denominators, never to be averaged:

• shortformkit (bylined Diego Brügger, 16 Oct): of 17,070 endpoints tested, 9,620 (56%) returned a full tool list with no key or login; 5,166 (30%) demanded auth; 2,284 (13%) were simply broken. The registry listed 28,933 remote endpoints; 4,945 declaring required headers were deliberately never tested.
• Cremit (bylined Ben Kim, 7 Oct): 15,696 of 22,027 responding servers (71.3%) opened a session with no header authentication.
• ProtocolProbe (16 Oct): 5,435 of 38,977 entries (13.9%) carry a defect the registry does not check.

56% is of endpoints chosen for testing; 71.3% is of servers that responded. Same direction, different populations. Quote either with its denominator or not at all.

The defect breakdown is the part you act on, all on ProtocolProbe's base of 38,977 entries: repository link 404s 4,298 (11.0%); listed version withdrawn upstream (npm deprecated / PyPI yanked) 663 (1.7%); active but declares no way to run it 459 (1.2%); linked repo archived 309 (0.8%); listed version cannot be installed 157 (0.4%).

Why it cannot self-correct — verified in the registry's own source, at the commit the audit cites (c384c4b): IsValidRepositoryURL in internal/validators/utils.go is a pure regex match with no HTTP call, and validation runs once at publish and is never re-run. The registry's own docs call the metadata "deliberately unopinionated" and the registry "in preview," so this is a documented design choice being quantified, not a bug being alleged.

The breakage detail, for when you debug a dead server: of the 2,284 that did not work, 534 were DNS or connection failures, 506 timed out at 10s, 465 returned a wrong-path 404, and 70 threw Cloudflare 530 origin-unreachable. 62 endpoints answered 402 Payment Required — "open" here means no signup, not free forever.

The velocity basis is not stars. The shortformkit data repo was measured at 0 stars and 0 forks, created today. What makes this tier is three independent measurements by different authors with different methods, plus a citable Zenodo deposit (DOI 10.5281/zenodo.23386799, 60.6 MB, CC BY 4.0). Both authors sell tooling built on the data; ProtocolProbe states "This is not a security finding" and that a 404 means missing or private, never deleted.

Do this now — Pin MCP server versions and resolve repos yourself; stop treating a registry entry as a liveness check. If you operate a remote MCP server, run the uncredentialed handshake against your own endpoint tonight and move credentials to the transport layer — Cremit found 3,705 credential fields taken as tool arguments across 529 servers, only three marked secret.

shortformkit, "State of remote MCP servers 2026" (shortformkit.com, 16 Oct) · ProtocolProbe (16 Oct, snapshot 4/6 Oct) · Cremit (cremit.io, 7 Oct) · Zenodo DOI 10.5281/zenodo.23386799 · also on r/mcp

02COMPANYGitHub's security agent hits GA twice, and three Copilot models die on 16 November

GitHub published three changelog entries on 15 October: agentic autofix GA, AI Scan for pull requests GA, and a dated model deprecation.

How autofix works, in GitHub's enumerated loop: explore relevant files, generate a proposed fix, validate the fix by rerunning CodeQL to confirm it closes the alert, iterate if needed, then open a draft PR carrying the validation steps it took. Drive it by assigning an alert to Copilot, by batching up to 25 alerts into one PR, or over the REST API with assignees: ["copilot-swe-agent[bot]"].

The gates, and there are several:

• Code Security / Advanced Security on Enterprise Cloud only; an enterprise admin must flip a new "Agentic autofix" Advanced Security policy before an org admin can enable it.
• Default-branch alerts only — alerts found on pull requests or other branches cannot be assigned.
• It replaces the free Generate Fix button with Assign to Copilot, and bills AI Credits from your Code Security budget plus Actions minutes. No per-fix price is published; do not quote one.
• The validate-before-PR guarantee does not cover custom CodeQL queries, the security-extended suite, or third-party tool alerts.

AI Scan is advisory. It covers what CodeQL does not — PHP, Shell/Bash, Terraform HCL, Dockerfiles, JSP, Blazor — but findings "cannot block pull request merges through ruleset requirements," and it skips forks and Dependabot PRs. No Copilot licence required.

The deprecation is the part that actually fires for most readers. On 2026-11-16, Opus 4.8, Opus 5 and GPT-5.6 Terra go dark "across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions)." Suggested moves: both Opus models → Opus 5.5; Terra → GPT-6.1 Sol or GPT-6 Luna.

The carve-out, verbatim, so you do not over-report it: "Claude Opus 4.8 will remain available to individual GitHub Copilot subscribers on annual plans" — Opus 4.8 only, no exception for Opus 5 or Terra. And this is a Copilot catalog decision, not a model retirement: Anthropic lists both Opus models ACTIVE with retirement no sooner than May and July 2027. The API path stays open; the model picker does not.

Do this now — Grep your agent configs, CI prompts and extension settings for the three model IDs before 16 November; agent modes are explicitly in scope, so a pinned ID in a harness breaks silently. The forced move is cheaper on GitHub's published rates: Opus 5.5 at $4.00/$0.20/$20.00 per 1M input/cached-input/output against Opus 5's $5.00/$0.50/$25.00. Replacements auto-enable for Enterprise and Business unless an admin turned the global default off.

GitHub changelog, "Agentic autofix for code scanning alerts" (github.blog, 15 Oct) · AI Scan for pull requests · Upcoming deprecation of selected Copilot models-80fff3a90d51-0fb5cf8a26c7