# lockdocs (npm · @sylphx/lockdocs)

Exact-version library docs from your lockfile — local, offline, no rate limits.

- Trust score: 81/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- npm · `@sylphx/lockdocs`: 81/100 (this document), [markdown](https://verifymcp.io/servers/sylphxai-lockdocs/sylphx-lockdocs.md), [page](https://verifymcp.io/servers/sylphxai-lockdocs/sylphx-lockdocs)

## Channel facts

- Registry: `npm`
- Package: `@sylphx/lockdocs`
- Version: `0.3.0`
- 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-09-26.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 5 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to SylphxAI/lockdocs).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 590 tokens (~196/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the lockdocs MCP server?

lockdocs runs locally as an npm package, launched with npx -y @sylphx/lockdocs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add sylphxai-lockdocs -- npx -y @sylphx/lockdocs
```

### Cursor

```json
{
  "mcpServers": {
    "sylphxai-lockdocs": {
      "command": "npx",
      "args": [
        "-y",
        "@sylphx/lockdocs"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sylphxai-lockdocs": {
      "command": "npx",
      "args": [
        "-y",
        "@sylphx/lockdocs"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add sylphxai-lockdocs -- npx -y @sylphx/lockdocs
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add sylphxai-lockdocs --command npx --arg -y --arg @sylphx/lockdocs
```

### Hermes

```yaml
mcp_servers:
  sylphxai-lockdocs:
    command: "npx"
    args: ["-y", "@sylphx/lockdocs"]
```

### Netclaw

```json
{
  "McpServers": {
    "sylphxai-lockdocs": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@sylphx/lockdocs"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add sylphxai-lockdocs -t stdio -c npx -a -y @sylphx/lockdocs
```

### Other

```json
{
  "mcpServers": {
    "sylphxai-lockdocs": {
      "command": "npx",
      "args": [
        "-y",
        "@sylphx/lockdocs"
      ]
    }
  }
}
```

## 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-09-26 (score 81, +12)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Dependency health: unverified → 1.00
- [functional] Package version: 0.2.1 → 0.3.0

### 2026-09-25 (score 69)

First indexed and scored.

## MCP tools (3)

### `resolve` (~119 tokens)

Resolve dependency versions

List the exact dependency versions this project pins (from package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lock, Cargo.lock, uv.lock, poetry.lock, requirements*.txt, go.mod) and whether their docs are available locally. Call it to learn which version of a library the code actually uses before writing code against it.

Input parameters:

- `filter` (string): Substring of a package name; also searches transitive dependencies.
- `root` (string): Absolute path of the project (defaults to the client's workspace root or the server's working directory).

### `docs` (~219 tokens)

Search version-exact docs

Answer a question from the docs of the exact installed version of a dependency: README, changelog, docs folder, and API reference (signatures + doc comments from .d.ts, Python, Rust and Go sources). Returns the most relevant sections within a token budget (hybrid keyword + embedding search), each cited as `package@version path:line`. Use it before using a library API you are not sure about for this version. Omit `package` to search all direct dependencies.

Input parameters:

- `package` (string): Package name, optionally ecosystem- or version-qualified: zod, npm:zod, pydantic, tokio, github.com/gin-gonic/gin. Comma-separate several.
- `query` (string, required): What you need, in words or identifiers, e.g. "strict object unknown keys" or "cookies async".
- `root` (string): Absolute path of the project (defaults to the client's workspace root or the server's working directory).
- `tokens` (integer): Answer budget in tokens (default 1200).

### `api` (~156 tokens)

Exact API of a symbol

The exact signature and doc comment of one symbol in the installed version, with overloads, members (for classes, interfaces, structs, traits) and other matches. Accepts `zod.z.object`, `z.object`, `tokio::spawn`, `axum::Router::route`, `pydantic.BaseModel.model_dump`, `gin.Context.JSON`.

Input parameters:

- `package` (string): Package to look in when the symbol has no package prefix.
- `root` (string): Absolute path of the project (defaults to the client's workspace root or the server's working directory).
- `symbol` (string, required): Symbol path, optionally prefixed by the package name.
- `tokens` (integer): Answer budget in tokens (default 1200).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/sylphxai-lockdocs/sylphx-lockdocs#diagnostics

## Score history

- 2026-09-26: 81
- 2026-09-25: 69

## Common questions

### What is the lockdocs MCP server?

lockdocs is an MCP server listed in the public MCP registry as io.github.SylphxAI/lockdocs. Exact-version library docs from your lockfile, local, offline, no rate limits. This page covers its npm package (@sylphx/lockdocs).

### Is the lockdocs MCP server safe to use?

lockdocs scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 lockdocs MCP server expose?

lockdocs exposes 3 tools: resolve, docs, api. Their descriptions and schemas cost roughly 494 tokens of context every time the server is loaded.

### Is the lockdocs MCP server still maintained?

lockdocs is still listed as active in the MCP registry. We last reached this channel on 26 September 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 lockdocs MCP server under?

lockdocs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@sylphx/lockdocs
- Socket report: https://socket.dev/npm/package/@sylphx/lockdocs
- Repository: https://github.com/SylphxAI/lockdocs
- Website: https://sylphxai.github.io/lockdocs/
- Changelog RSS feed: https://verifymcp.io/servers/sylphxai-lockdocs/sylphx-lockdocs.xml
- Changelog JSON feed: https://verifymcp.io/servers/sylphxai-lockdocs/sylphx-lockdocs.json
- HTML version of this page: https://verifymcp.io/servers/sylphxai-lockdocs/sylphx-lockdocs