Pg Migration Lock Lint runs on your own machine — the client starts it, so there is no endpoint to ping. 372 installs a week from npm. Last commit 22 Sep 2026.
Names every statement in a Rails, Django or raw SQL migration that takes a table-blocking Postgres l
We read the source, 13 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
const target = path.join(dir, 'csaf-conformance-' + stamp + '.' + (fmt === 'json' ? 'json' : fmt === 'html' ? 'html' : 'csv'));
o.innerHTML=s+'</table>'};
…S Firebase's defaults, and this list has no **/.* entry. Every dotfile under the public root — .env, .env.production, .npmrc, .git — is uploaded and served.","fix":"Add \"**/.*\" back to the ignore array."},
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add pg-migration-lock-lint -- npx -y @readystack/pg-migration-lock-lint
{
"mcpServers": {
"pg-migration-lock-lint": {
"args": [
"-y",
"@readystack/pg-migration-lock-lint"
],
"command": "npx"
}
}
}
[mcp_servers.pg-migration-lock-lint]
command = "npx"
args = ["-y", "@readystack/pg-migration-lock-lint"]
{
"mcpServers": {
"pg-migration-lock-lint": {
"args": [
"-y",
"@readystack/pg-migration-lock-lint"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"pg-migration-lock-lint": {
"args": [
"-y",
"@readystack/pg-migration-lock-lint"
],
"command": "npx"
}
}
}
Names every column, index, view and seed row in a .sql migration that stores card data, with its PCI
Lints PostgreSQL migrations for dangerous locking operations and suggests safe rewrites.
Names every line in the file you have open that starts a recurring cloud charge, with the published
Names every schedule line in the file you have open that fires at the wrong hour, twice, or never at
Names the Gateway API field that replaces each retired ingress-nginx annotation — or tells you there
Reads the licence field in the open manifest and names every deprecated SPDX id, invalid string, PEP
Security reviews, threat models over a repo or website, and remediation tracking, in your editor.
Free disposable email for AI agents: a throwaway inbox to read verification codes over MCP.
Answers built from our own checks of this server.