io.github.cxk280/locksmith
NPM · LOCKSMITH-MCP
Lints PostgreSQL migrations for dangerous locking operations and suggests safe rewrites.
Available components
Last scanned (3 hours ago)
Scores higher than 69% of npm servers
Category Databases
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 32 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 128 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 211 tokens (~52/item across 4 items; 2 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.93 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/locksmith-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 101 packages
| Packages resolved | 101 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_migration Analyze a SQL migration for locking hazards ~112
Lint a PostgreSQL migration for operations that take dangerous locks (table rewrites, blocking index builds, validating constraints, destructive/breaking changes) and return a PASS/REVIEW/BLOCK verdict with per-statement findings and safe rewrites. Call this before applying or approving any migration.
| Name | Type | Req | Description |
|---|---|---|---|
| assumeLargeTables | boolean | – | Assume target tables are large/hot, so scans and rewrites are flagged. Default true (fail safe). |
| sql | string | yes | The full SQL migration script to analyze. |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | – |
| stats | object | yes | – |
| summary | string | yes | – |
| verdict | string | yes | – |
No examples provided.
explain_lock Explain a PostgreSQL lock mode ~66
Given a lock mode name (e.g. 'ACCESS EXCLUSIVE') or a fragment of an operation, explain what it blocks and which operations acquire it.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A lock mode name or operation fragment, e.g. 'ACCESS EXCLUSIVE' or 'create index'. |
No output schema declared.
No examples provided.
How do I install the io.github.cxk280/locksmith MCP server?
io.github.cxk280/locksmith runs locally as an npm package, launched with npx -y locksmith-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · locksmith-mcp
claude mcp add cxk280-locksmith -- npx -y locksmith-mcp
What is the io.github.cxk280/locksmith MCP server?
io.github.cxk280/locksmith is an MCP server listed in the public MCP registry as io.github.cxk280/locksmith. Lints PostgreSQL migrations for dangerous locking operations and suggests safe rewrites. This page covers its npm package (locksmith-mcp).
Is the io.github.cxk280/locksmith MCP server safe to use?
io.github.cxk280/locksmith scores 81 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.cxk280/locksmith MCP server expose?
io.github.cxk280/locksmith exposes 2 tools: analyze_migration, explain_lock. Their descriptions and schemas cost roughly 178 tokens of context every time the server is loaded.
Is the io.github.cxk280/locksmith MCP server still maintained?
io.github.cxk280/locksmith is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.cxk280/locksmith MCP server under?
io.github.cxk280/locksmith declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.