# io.github.cxk280/locksmith (npm · locksmith-mcp)

Lints PostgreSQL migrations for dangerous locking operations and suggests safe rewrites.

- Trust score: 71/100 (medium)
- Change this week: +18
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `locksmith-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/cxk280-locksmith/locksmith-mcp.md), [page](https://verifymcp.io/servers/cxk280-locksmith/locksmith-mcp)

## Channel facts

- Registry: `npm`
- Package: `locksmith-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (103 of 107), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (103 of 107), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 34 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 211 tokens (~52/item across 4 items; 2 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (50% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add cxk280-locksmith -- npx -y locksmith-mcp
```

### Codex

```bash
codex mcp add cxk280-locksmith -- npx -y locksmith-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cxk280-locksmith": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "locksmith-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cxk280-locksmith --command npx --arg -y --arg locksmith-mcp
```

### Hermes

```yaml
mcp_servers:
  cxk280-locksmith:
    command: "npx"
    args: ["-y", "locksmith-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "cxk280-locksmith": {
      "command": "npx",
      "args": [
        "-y",
        "locksmith-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 71, +30)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.27
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: MIT

### 2026-08-02 (score 41, +36)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100

### 2026-08-01 (score 5, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 6, −47)

- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-30 (score 53, +29)

- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 24, −29)

- [functional regression] Schema quality: 100 → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-27 (score 53)

First indexed and scored.

## MCP tools (2)

### `analyze_migration` (~112 tokens)

Analyze a SQL migration for locking hazards

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.

Input parameters:

- `assumeLargeTables` (boolean): Assume target tables are large/hot, so scans and rewrites are flagged. Default true (fail safe).
- `sql` (string, required): The full SQL migration script to analyze.

Output parameters:

- `findings` (array)
- `stats` (object)
- `summary` (string)
- `verdict` (string)

### `explain_lock` (~66 tokens)

Explain a PostgreSQL lock mode

Given a lock mode name (e.g. 'ACCESS EXCLUSIVE') or a fragment of an operation, explain what it blocks and which operations acquire it.

Input parameters:

- `query` (string, required): A lock mode name or operation fragment, e.g. 'ACCESS EXCLUSIVE' or 'create index'.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cxk280-locksmith/locksmith-mcp#diagnostics

## Score history

- 2026-08-03: 71
- 2026-08-02: 41
- 2026-08-01: 5
- 2026-07-31: 6
- 2026-07-30: 53
- 2026-07-28: 24
- 2026-07-27: 53

## Links

- npm package: https://www.npmjs.com/package/locksmith-mcp
- Socket report: https://socket.dev/npm/package/locksmith-mcp
- Repository: https://github.com/cxk280/locksmith
- Changelog RSS feed: https://verifymcp.io/servers/cxk280-locksmith/locksmith-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/cxk280-locksmith/locksmith-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/cxk280-locksmith/locksmith-mcp