lockdocs
NPM · @SYLPHX/LOCKDOCS · SCANNED SEP 26
Exact-version library docs from your lockfile — local, offline, no rate limits.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SylphxAI/lockdocs). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
npm · @sylphx/lockdocs
claude mcp add sylphxai-lockdocs -- npx -y @sylphx/lockdocs
{
"mcpServers": {
"sylphxai-lockdocs": {
"command": "npx",
"args": [
"-y",
"@sylphx/lockdocs"
]
}
}
} {
"servers": {
"sylphxai-lockdocs": {
"command": "npx",
"args": [
"-y",
"@sylphx/lockdocs"
]
}
}
} codex mcp add sylphxai-lockdocs -- npx -y @sylphx/lockdocs
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sylphxai-lockdocs": {
"type": "local",
"command": [
"npx",
"-y",
"@sylphx/lockdocs"
],
"enabled": true
}
}
} openclaw mcp add sylphxai-lockdocs --command npx --arg -y --arg @sylphx/lockdocs
mcp_servers:
sylphxai-lockdocs:
command: "npx"
args: ["-y", "@sylphx/lockdocs"] {
"McpServers": {
"sylphxai-lockdocs": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@sylphx/lockdocs"
]
}
}
} assistant mcp add sylphxai-lockdocs -t stdio -c npx -a -y @sylphx/lockdocs
{
"mcpServers": {
"sylphxai-lockdocs": {
"command": "npx",
"args": [
"-y",
"@sylphx/lockdocs"
]
}
}
} 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.
- 26 Sept 26 +12
- Known CVEs: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Dependency health: unverified → 1.00 ▲ functional
- Package version: 0.2.1 → 0.3.0 functional
- 25 Sept 26 69
First indexed and scored.
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 26 Sept 2026 · Analysed npm/@sylphx/lockdocs@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | SylphxAI/lockdocs |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SylphxAI/mcp-kit/.github/workflows/release.yml@refs/tags/v0 |
| Rekor log index | 2963728271 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6fd452146d48a48e7c654258b2d501d54c680ef526d78313d461e37f8b2817e2a67072c0bc0d3cf8559856368e677881873426731afe1d9a065e9aaea |
Background: How many MCP packages publish verified provenance →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| 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 →
api Exact API of a symbol ~156
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Symbol path, optionally prefixed by the package name. |
| tokens | integer | – | Answer budget in tokens (default 1200). |
No output schema declared.
No examples provided.
docs Search version-exact docs ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | – | Package name, optionally ecosystem- or version-qualified: zod, npm:zod, pydantic, tokio, github.com/gin-gonic/gin. Comma-separate several. |
| query | string | yes | 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). |
No output schema declared.
No examples provided.
resolve Resolve dependency versions ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.