io.github.CloudCorpRecords/libdocs
NPM · @RENETURCIOS/LIBDOCS · 2 COMPONENTS
Resolve library names and fetch current, version-specific documentation via Context7.
Available components
Last scanned (4 hours ago)
Scores higher than 33% of npm servers
Category Code Search and Documentation
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
- 30 of 93 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 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 163 tokens (~81/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 50
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 5 Nov 2026 · Analysed npm/@reneturcios/libdocs@0.1.0
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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
get-library-docs ~116
Fetch current documentation and code examples for a library using its Context7-compatible library ID.
| Name | Type | Req | Description |
|---|---|---|---|
| context7CompatibleLibraryID | string | yes | Context7-compatible library ID to fetch documentation for, as returned by resolve-library-id, for example "/vercel/next.js". |
| tokens | number | – | Optional maximum number of documentation tokens to return; defaults to 10000 and values below 10000 are raised to 10000. |
| topic | string | – | Optional topic to focus the returned documentation on, for example "routing". |
No output schema declared.
No examples provided.
resolve-library-id ~47
Resolve a library name into a Context7-compatible library ID, returning the matching libraries.
| Name | Type | Req | Description |
|---|---|---|---|
| libraryName | string | yes | Name of the library to resolve into a Context7-compatible library ID. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/libdocs MCP server?
io.github.CloudCorpRecords/libdocs runs locally as an npm package, launched with npx -y @reneturcios/libdocs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/libdocs
claude mcp add cloudcorprecords-libdocs -- npx -y @reneturcios/libdocs
What is the io.github.CloudCorpRecords/libdocs MCP server?
io.github.CloudCorpRecords/libdocs is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/libdocs. Resolve library names and fetch current, version-specific documentation via Context7. This page covers its npm package (@reneturcios/libdocs).
Is the io.github.CloudCorpRecords/libdocs MCP server safe to use?
io.github.CloudCorpRecords/libdocs scores 65 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.CloudCorpRecords/libdocs MCP server expose?
io.github.CloudCorpRecords/libdocs exposes 2 tools: resolve-library-id, get-library-docs. Their descriptions and schemas cost roughly 163 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/libdocs MCP server still maintained?
io.github.CloudCorpRecords/libdocs 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.CloudCorpRecords/libdocs MCP server under?
io.github.CloudCorpRecords/libdocs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.