Delete the Supabase-backed registry/ MCP server (replaced by static registry.json)

Delete the Supabase-backed registry/ MCP server

Studio is moving its store to consume this repo's static registry.json directly (see #476, #477). Once that lands, the live Supabase-backed registry server — the registry/ workspace, deployed at https://sites-registry.deco.site/mcp — becomes unused and can be deleted.

What to delete

The whole registry/ workspace + its Supabase pipeline:

• registry/server/** (registry-binding.ts, lib/supabase-client.ts, lib/mappers.ts, lib/registry-client.ts, lib/allowlist.ts, lib/blacklist.ts, lib/verified.ts, main.ts, …)
• registry/scripts/** (populate-supabase.ts, enrich-with-ai.ts, generate-allowlist.ts, publish-verified.ts, create-table.sql)
• the registry entry in deploy.json and any publish-registry/deploy wiring for it
• registry from package.json workspaces
• the Supabase secrets (SUPABASE_URL / SUPABASE_*) once nothing references them

⚠️ Prerequisite (do NOT merge before this)

Studio's mesh must first stop consuming sites-registry.deco.site/mcp. That happens in the registry-gutting Phase 4 (removing the seeded community-registry connection). Before deleting:

• Confirm Studio mesh Phase 4 (remove seeded registry connections) has shipped.
• Confirm no other consumer hits sites-registry.deco.site/mcp (grep deploys / check traffic).

Context

A sweep of prod installs showed the static registry.json already covers virtually all community MCPs people actually use (the only popular gap, GitHub's official MCP, was added in #477). So the live Supabase mirror of the official registry (allowlist + AI enrichment) is no longer worth maintaining — the curated static catalog replaces it.

Related follow-up (separate)

The publish flow (scripts/publish-one.ts / publish-all.ts → Studio's …/registry/publish-request) also becomes obsolete when Studio removes the publish-request endpoint (registry-gutting Phase 3). Worth retiring in the same cleanup, but track separately.

First confirm Studio mesh Phase 4 has shipped and grep deploys or check traffic for remaining consumers of sites-registry.deco.site/mcp. Then inspect registry/server/, registry/scripts/, deploy.json, package.json workspaces, and publish-registry wiring; done means the registry workspace and Supabase references are removed without affecting the static registry flow.