Pg Migration Lock Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.2Updated Oct 24, 2026

Names every statement in a Rails, Django or raw SQL migration that takes a table-blocking Postgres l

VerifiedSTDIODesktop onlyDatabasesDeveloper Tools

Overview

AI-generated overview

A local MCP server that names every statement in a Rails, Django or raw SQL migration that takes a table-blocking Postgres lock.

What you can do
Inspects migration files and reports which statements would take a table-blocking Postgres lock, so they can be reviewed before running. Covers Rails, Django and raw SQL migrations. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when reviewing or preparing database migrations for Postgres and you want an assistant to flag statements that could block a table during deployment.
Requirements
Runs as a local process on the user's machine via npx from the npm package @readystack/pg-migration-lock-lint. Desktop only; no authentication, environment variables or headers are declared.
Before you install
The README describes unrelated VS Code themes, so the supplied documentation does not match the stated purpose; verify what the package actually does before installing. It is a local process started on your machine, so review the package before running it.

Installation

In SourceWeft

  1. Open Pg Migration Lock Lint in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 19, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.