Render the SQL Liquibase would run for pending changesets as structured per-changeset summaries with SQL Server batch linting; preview only, no changes applied.
Apache 2.0
763,219 tools. Updated 2026-11-10 10:47
"Liquibase" matching MCP tools:
- Validates Liquibase changelogs and returns compact structured pass/fail results with per-changeset errors such as duplicate IDs and checksum drift.Apache 2.0
- Lists pending Liquibase changesets for a target database and returns structured JSON showing up-to-date status or unapplied changes, so agents can verify migration state.Apache 2.0
- Track Flyway and Liquibase migrations, detect schema drift, and validate checksums to ensure database consistency.ISC
- Retrieve the runtime status of Liquibase database migrations from a Spring Boot application's Actuator endpoint.MIT
- Execute SQL files for database migrations, schema changes, or data imports. Supports atomic transactions, validation preview, and pattern stripping for compatibility.MIT
- Analyzes Liquibase YAML changelogs to identify lock contention risks, data loss potential, and unsafe patterns. Supports all major change types and inline SQL analysis.MIT
- Scans repository database migrations to classify each change as rollback-safe or destructive, returning blocking migrations and deployment strategy for rollback readiness assessment.MIT
- Analyze Liquibase changelogs to detect lock risks, data loss potential, and unsafe patterns before migration execution.MIT
- Probe databases for migration tool tracker tables to identify managed migrations, returning detected tools, schema, table, count, and latest version.MIT
- Inspect Flyway and Liquibase migration status across Spring Boot containers and beans to diagnose failures, checksum or version differences, and out-of-order states without running SQL or migrations.Apache 2.0
- Available with Bootify Professional. Snapshot the current database schema so subsequent schema changes generate a new Flyway, Liquibase or Mongock changelog. Available only when getProject BREAKPOINTS reports AVAILABLE. Generated changelogs are blueprints and must be adapted to production data. Use this tool only after the user has explicitly confirmed adding a breakpoint.ConnectorNo auth
- Create a IBIS diagram as PNG image. IBIS (Issue-Based Information System) maps out any decision, discussion, or thought process using just four node types: Questions, Answers (Ideas), Pros, and Cons. Attaching Questions to any node lets you drill into any aspect at any depth. You provide VGL (Vithanco Graph Language) code using the IBIS notation and the tool renders it to an PNG image. ## How to Build an IBIS Diagram 1. Start with a root Question (used as the graph title). 2. Add Answers (Ideas) that respond to the question. 3. Add Pro and Con arguments for each answer. 4. Attach further Questions to any node to drill deeper. 5. Keep going until the topic is explored to the depth you need. ## VGL Syntax ``` vgraph <id>: IBIS "<title>" { <nodes and edges> } ``` ### Node Types - `Question` — Questions are the key driver of IBIS. They are the starting point and can be connected to all other node types. - `Answer` — An idea or answer for a question. Answers are evaluated through pro and con arguments. - `Pro` — An argument in favour of an answer. Pros help evaluate and decide between competing answers. - `Con` — An argument against an answer. Cons help evaluate and decide between competing answers. ``` node <id>: Question "<label>" node <id>: Answer "<label>" node <id>: Pro "<label>" node <id>: Con "<label>" ``` ### Edges Edge types are inferred from node types — just write `edge <from> -> <to>`. Valid connections: - Question → Question — A question can raise a further question, enabling infinite depth of inquiry. - Answer → Question — An answer can raise a further question — e.g., to probe its assumptions. - Pro → Question — A pro argument can raise a further question — e.g., to test its validity. - Con → Question — A con argument can raise a further question — e.g., to explore how to overcome it. - Question → Answer — A question is answered by this idea or answer. - Answer → Pro — This answer is supported by a pro argument. - Answer → Con — This answer is objected to by a con argument. ``` edge <from_id> -> <to_id> ``` ## The Drill-Down Mechanism The power of IBIS is that you can attach a Question to **any** node type: - Question a Question: "Shouldn't we rather discuss X?" - Question an Answer: "What would we need to implement this?" - Question a Pro: "Is this advantage really significant?" - Question a Con: "Can we mitigate this disadvantage?" Each sub-question starts its own Answer/Pro/Con branch, allowing unlimited depth. ## Complete Example ``` vgraph techChoice: IBIS "Which database should we use?" { node q1: Question "Which database should we use?" node a1: Answer "PostgreSQL" node a2: Answer "MongoDB" edge q1 -> a1 edge q1 -> a2 node pro1: Pro "ACID compliance" node pro2: Pro "Mature ecosystem" node con1: Con "Schema migrations can be complex" edge a1 -> pro1 edge a1 -> pro2 edge a1 -> con1 node pro3: Pro "Flexible schema" node con2: Con "Weaker transaction support" edge a2 -> pro3 edge a2 -> con2 node q2: Question "How to handle schema migrations?" edge con1 -> q2 node a3: Answer "Use Flyway or Liquibase" edge q2 -> a3 node pro4: Pro "Industry-standard tooling" edge a3 -> pro4 } ``` ## Rules 1. ALWAYS start with a root Question — it frames the entire diagram 2. Follow the structure: Question -> Answer -> Pro/Con 3. Use Questions to drill down — attach them to any node that needs exploration 4. Keep labels concise — Questions as questions, Answers as noun phrases, Pros/Cons as short statements 5. Use meaningful IDs (q1, mainIdea, costCon — not n1, n2, n3) 6. Each Answer should have at least one Pro or Con to be useful 7. Avoid orphan nodes — every node must connect to the treeConnectorNo auth