io.github.rog0x/docs
NPM · @ROG0X/MCP-DOCS-TOOLS · SCANNED AUG 3
JSDoc, README, changelog generation for AI agents
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 133 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 418 tokens (~83/item across 5 items; 5 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
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @rog0x/mcp-docs-tools
claude mcp add rog0x-docs -- npx -y @rog0x/mcp-docs-tools
codex mcp add rog0x-docs -- npx -y @rog0x/mcp-docs-tools
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rog0x-docs": {
"type": "local",
"command": [
"npx",
"-y",
"@rog0x/mcp-docs-tools"
],
"enabled": true
}
}
} openclaw mcp add rog0x-docs --command npx --arg -y --arg @rog0x/mcp-docs-tools
mcp_servers:
rog0x-docs:
command: "npx"
args: ["-y", "@rog0x/mcp-docs-tools"] {
"mcpServers": {
"rog0x-docs": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-docs-tools"
]
}
}
} 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.
- 2 Aug 26 +59
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −16
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
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 3 Aug 2026 · Analysed npm/@rog0x/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
analyze_code_comments ~82
Analyze code comments: compute comment-to-code ratio, find TODO/FIXME/HACK markers, detect functions without documentation, and suggest where docs are needed.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The source code to analyze |
| language | string | — | Programming language of the code (e.g. 'typescript', 'python', 'go', 'rust', 'java') |
No output schema declared.
No examples provided.
analyze_readme ~57
Analyze a README.md file content: check for required sections (install, usage, license), rate completeness 0-100, and suggest missing sections.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The full text content of the README.md file to analyze |
No output schema declared.
No examples provided.
generate_api_docs ~99
Generate REST API documentation in Markdown from endpoint descriptions. Includes method, URL, parameters, request/response examples, and status codes.
| Name | Type | Req | Description |
|---|---|---|---|
| apiDescription | string | — | General description of the API |
| apiTitle | string | yes | Title for the API documentation |
| baseUrl | string | — | Base URL for the API, e.g. 'https://api.example.com/v1' |
| endpoints | array | yes | Array of endpoint definitions to document |
No output schema declared.
No examples provided.
generate_changelog ~82
Generate CHANGELOG entries from git-style commit messages. Categorizes commits as Added/Changed/Fixed/Removed/Deprecated/Security and groups by version following Keep a Changelog format.
| Name | Type | Req | Description |
|---|---|---|---|
| projectName | string | — | Optional project name for the changelog header |
| versions | array | yes | Array of version objects, each containing version, date, and commit messages |
No output schema declared.
No examples provided.
generate_jsdoc ~98
Generate JSDoc/TSDoc comments for a function signature. Parses the signature and produces @param, @returns, @throws, and @example tags.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | Optional description of what the function does |
| functionSignature | string | yes | The function signature to document, e.g. 'async function fetchUser(id: string): Promise<User>' |
| includeExample | boolean | — | Whether to include an @example tag |
No output schema declared.
No examples provided.