## What happened?

After upgrading to **v1.81.14-stable** (`ghcr.io/berriai/litellm-non_root`), the proxy started returning `500 Internal Server Error` on `/v2/login` and silently returning empty arrays from `/v1/mcp/server`. Both failures were caused by missing DB columns that should have been added by `litellm_proxy_extras` migrations.

### Root cause

The extras migrations were **recorded as applied** in `_prisma_migrations` (i.e. `prisma migrate deploy` reported "No pending migrations to apply") but the actual `ALTER TABLE` SQL was never executed against the database. The schema and DB were silently out of sync.

### Symptoms

**Login broken (500 on /v2/login):** ``` prisma.errors.DataError: The column `LiteLLM_VerificationToken.project_id` does not exist in the current database. ``` Then after fixing `project_id`: ``` prisma.errors.DataError: The column `LiteLLM_VerificationToken.last_active` does not exist in the current database. ```

**MCP servers silently returning empty list:** ``` prisma.errors.DataError: The column `LiteLLM_MCPServerTable.spec_path` does not exist in the current database. ``` Note: `get_all_mcp_servers()` in `db.py` catches the exception at `debug` leve…