mcp-migration-advisor 0.2.12 → 0.2.14

package/build/analyzers/data-loss.js

@@ -28,11 +28,12 @@ export function analyzeDataLoss(migration) {
             }
             case "DROP_TABLE": {
                 const cascade = upper.includes("CASCADE");
+                const dropTableName = stmt.tableName ?? "unknown";
                 issues.push({
                     risk: "CERTAIN",
                     statement: truncate(stmt.raw),
                     tableName: stmt.tableName,
-                    description: `Dropping table '${stmt.tableName}' permanently deletes all data.${cascade ? " CASCADE will also drop dependent objects." : ""}`,
+                    description: `Dropping table '${dropTableName}' permanently deletes all data.${cascade ? " CASCADE will also drop dependent objects." : ""}`,
                     mitigation: "Ensure a backup exists. Consider renaming the table first and dropping in a later migration.",
                 });
                 break;
@@ -79,8 +80,9 @@ export function analyzeDataLoss(migration) {
                 // Skip data manipulation checks for CREATE statements to avoid false positives.
                 if (/^CREATE\b/i.test(stmt.raw.trim()))
                     break;
-                // Detect TRUNCATE
-                if (upper.includes("TRUNCATE")) {
+                // Detect TRUNCATE — use word-boundary match to avoid false positives
+                // on table/column names containing "truncate" (e.g. truncate_log).
+                if (/\bTRUNCATE\b/i.test(stmt.raw)) {
                     const tableMatch = stmt.raw.match(/TRUNCATE\s+(?:TABLE\s+)?(?:`|"|)?(?:\w+\.)?(\w+)/i);
                     issues.push({
                         risk: "CERTAIN",

package/build/analyzers/lock-risk.js

@@ -85,11 +85,12 @@ function analyzeStatement(stmt) {
             break;
         }
         case "DROP_TABLE": {
+            const dropTableName = stmt.tableName ?? "unknown";
             risks.push({
                 severity: "HIGH",
                 statement: truncate(stmt.raw),
                 tableName: stmt.tableName,
-                risk: `DROP TABLE '${stmt.tableName}' is irreversible and acquires ACCESS EXCLUSIVE lock.`,
+                risk: `DROP TABLE '${dropTableName}' is irreversible and acquires ACCESS EXCLUSIVE lock.`,
                 recommendation: "Ensure no foreign keys reference this table. Consider renaming first (expand-contract) to allow rollback.",
             });
             if (stmt.details.cascade === "true") {

package/build/index.js

@@ -6,9 +6,12 @@
  *   analyze_migration  — Parse and analyze a SQL migration for risks
  *   score_risk          — Calculate risk score for a migration
  */
+import { createRequire } from "module";
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { z } from "zod";
+const require = createRequire(import.meta.url);
+const { version: packageVersion } = require("../package.json");
 import { parseMigration } from "./parsers/flyway-sql.js";
 import { parseLiquibaseXml } from "./parsers/liquibase-xml.js";
 import { parseLiquibaseYaml } from "./parsers/liquibase-yaml.js";
@@ -33,7 +36,7 @@ function formatParserWarnings(migration) {
 }
 // Handle --help
 if (process.argv.includes("--help") || process.argv.includes("-h")) {
-    console.log(`mcp-migration-advisor v0.2.12 — MCP server for database migration risk analysis
+    console.log(`mcp-migration-advisor v${packageVersion} — MCP server for database migration risk analysis
 
 Usage:
   mcp-migration-advisor [options]
@@ -52,10 +55,10 @@ Tools provided:
 }
 const server = new McpServer({
     name: "mcp-migration-advisor",
-    version: "0.2.12",
+    version: packageVersion,
 });
 // Tool 1: analyze_migration
-server.tool("analyze_migration", "Analyze a SQL migration file for lock risks, data loss potential, and unsafe patterns. Supports Flyway (V__*.sql) and plain SQL.", {
+server.tool("analyze_migration", "Analyze a SQL migration file for lock risks, data loss potential, and unsafe patterns. Detects: ACCESS EXCLUSIVE locks (DROP TABLE, ADD COLUMN NOT NULL, type changes, CREATE INDEX without CONCURRENTLY), data loss operations (TRUNCATE, DELETE without WHERE, UPDATE without WHERE, DROP COLUMN), and cascade risks. Supports Flyway versioned (V__*.sql) and repeatable (R__*.sql) migrations, as well as plain SQL files.", {
     filename: z.string().describe("Migration filename (e.g., V2__add_user_email.sql)"),
     sql: z.string().describe("The SQL content of the migration file"),
 }, async ({ filename, sql }) => {
@@ -126,7 +129,7 @@ server.tool("analyze_migration", "Analyze a SQL migration file for lock risks, d
     }
 });
 // Tool 2: analyze_liquibase
-server.tool("analyze_liquibase", "Analyze a Liquibase XML changelog for lock risks, data loss potential, and unsafe patterns. Supports createTable, dropTable, addColumn, dropColumn, modifyDataType, createIndex, addForeignKeyConstraint, renameTable, renameColumn, and more.", {
+server.tool("analyze_liquibase", "Analyze a Liquibase XML changelog for lock risks, data loss potential, and unsafe patterns. Supports all major change types: createTable, dropTable, addColumn, dropColumn, modifyDataType, addNotNullConstraint, createIndex, dropIndex, addForeignKeyConstraint, dropForeignKeyConstraint, renameTable, renameColumn. Inline <sql> changeSets are also analyzed for TRUNCATE, DELETE without WHERE, and UPDATE without WHERE. Returns lock risk severity (ACCESS EXCLUSIVE, SHARE locks) and data loss risk per operation.", {
     xml: z.string().describe("The Liquibase XML changelog content"),
 }, async ({ xml }) => {
     try {
@@ -183,7 +186,7 @@ server.tool("analyze_liquibase", "Analyze a Liquibase XML changelog for lock ris
     }
 });
 // Tool 3: analyze_liquibase_yaml
-server.tool("analyze_liquibase_yaml", "Analyze a Liquibase YAML changelog for lock risks, data loss potential, and unsafe patterns. Supports createTable, dropTable, addColumn, dropColumn, modifyDataType, createIndex, addForeignKeyConstraint, renameTable, renameColumn, and more.", {
+server.tool("analyze_liquibase_yaml", "Analyze a Liquibase YAML changelog for lock risks, data loss potential, and unsafe patterns. Supports all major change types: createTable, dropTable, addColumn, dropColumn, modifyDataType, addNotNullConstraint, createIndex, dropIndex, addForeignKeyConstraint, dropForeignKeyConstraint, renameTable, renameColumn. Inline sql changeSets are also analyzed for TRUNCATE, DELETE without WHERE, and UPDATE without WHERE. Returns lock risk severity (ACCESS EXCLUSIVE, SHARE locks) and data loss risk per operation.", {
     yaml: z.string().describe("The Liquibase YAML changelog content"),
 }, async ({ yaml }) => {
     try {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-migration-advisor",
-  "version": "0.2.12",
+  "version": "0.2.14",
   "description": "MCP server for database migration risk analysis — Flyway and Liquibase XML/YAML/SQL support with lock detection and conflict analysis",
   "mcpName": "io.github.dmitriusan/mcp-migration-advisor",
   "main": "build/index.js",