schema-drift vs LiteScope
schema-drift is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
schema-drift is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. LiteScope is an MCP server published by croc100. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  LiteScope | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.9.0 Downloads/month (npm): 254 Downloads/week (npm): 105 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | schema-driftno longer listed · | LiteScope |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | On your machine (litescope) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | AGPL-3.0 |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/croc100/litescope |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of schema-drift
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Database migration safety plugin that detects dangerous schema changes, warns about locking risks, and suggests zero-downtime migration patterns across Rails, Django, Laravel, and…
-
Database migration automation, observability, and cross-database migration strategies
-
Database migration automation, observability, and cross-database migration strategies
-
MigraFlow - Database Migration AI
AI-powered database migration. Analyze schemas, generate SQL, calculate risks.
-
Schema migration management — generate, validate, dry-run, and rollback database migrations
-
Safe PostgreSQL migrations: schema drift, lock analysis, safe rewrites, data checksums. Read-only.
What each says it does
schema-drift
Generate database migrations, detect schema drift, validate migration safety, and auto-document schemas
LiteScope
Operations toolchain for SQLite, Cloudflare D1 & Turso: inspect, diff, migrate, monitor & repair.
How to run each
schema-drift
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
LiteScope As a local MCP server: npm package
claude mcp add --env "CLOUDFLARE_API_TOKEN=<YOUR_CLOUDFLARE_API_TOKEN>" --transport stdio litescope -- npx -y litescope mcpRequires: CLOUDFLARE_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of schema-drift publish no settings it asks for, so we do not compare settings.
What it can do: schema-drift · What it can do: LiteScope · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.