io.github.vpatser1/mcp-api-doc-generator
NPM · MCP-API-DOC-GENERATOR
Generate OpenAPI 3.1 specs, endpoint docs, TypeScript SDKs, and test suites from code
Available components
Last scanned (20 hours ago)
Scores higher than 46% of npm servers
Category Developer Tools
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 Security80
- 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
- 40 of 121 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 108 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 538 tokens (~107/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 0
- Stability: 0.97 → pass security
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Supply Chain Security fell 1.
- 18 Nov 26 −1
- Stability: pass → 0.93 functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 −1
- Stability: pass → 0.90 functional
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
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 21 Nov 2026 · Analysed npm/mcp-api-doc-generator@1.1.4
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 121 packages
| Packages resolved | 121 |
|---|---|
| Stale | 40 |
| 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 →
document_endpoint ~167
Generates full documentation for a single API endpoint in Markdown. Includes parameter tables, request/response examples with realistic data, error response documentation (400, 401, 403, 404, 500), cURL command example, JavaScript fetch example, and Python requests example.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_type | string | – | Authentication type required |
| description | string | yes | What this endpoint does |
| method | string | yes | HTTP method (GET, POST, PUT, PATCH, DELETE) |
| parameters | array | – | Path, query, or header parameters |
| path | string | yes | URL path (e.g. /users/{id}) |
| request_body | object | – | Request body schema |
| response | object | – | Success response schema |
| tags | array | – | Tags for grouping |
No output schema declared.
No examples provided.
generate_openapi ~105
Generates a complete OpenAPI 3.1 specification from endpoint definitions. Produces properly structured output with paths, parameters, request/response schemas using $ref components, authentication sections, server URLs, tags, and grouping. Supports YAML and JSON output.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | array | yes | Array of endpoint definitions to include in the spec |
| format | string | – | Output format (default: yaml) |
| info | object | – | OpenAPI info block (title, version, description) |
No output schema declared.
No examples provided.
generate_sdk ~92
Generates a TypeScript SDK client from endpoint definitions. Produces typed interfaces for all request/response models, a client class with methods for each endpoint, error handling helpers (ApiError class with retry support), and authentication wrappers (Bearer, API Key, Basic).
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | Base URL for API calls (default: https://api.example.com) |
| endpoints | array | yes | Array of endpoint definitions |
No output schema declared.
No examples provided.
generate_tests ~97
Generates comprehensive API test suites for endpoints. Creates happy path tests, validation tests (missing required fields), edge case tests (empty values, null values, extra fields), authentication tests, HTTP method tests, and response structure checks. Includes mock data generator functions. Outputs as Jest or Vitest test files.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | array | yes | Array of endpoint definitions to test |
| framework | string | – | Test framework to use (default: vitest) |
No output schema declared.
No examples provided.
validate_api ~77
Validates an OpenAPI specification (YAML or JSON). Checks schema correctness, missing descriptions, inconsistent naming conventions, missing error responses, security scheme completeness, and server URLs. Returns categorized issues (errors, warnings, suggestions) with specific fix suggestions for each.
| Name | Type | Req | Description |
|---|---|---|---|
| spec | string | yes | OpenAPI spec content (YAML or JSON string) |
No output schema declared.
No examples provided.
How do I install the io.github.vpatser1/mcp-api-doc-generator server?
io.github.vpatser1/mcp-api-doc-generator runs locally as an npm package, launched with npx -y mcp-api-doc-generator. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-api-doc-generator
claude mcp add vpatser1-mcp-api-doc-generator -- npx -y mcp-api-doc-generator
What is the io.github.vpatser1/mcp-api-doc-generator server?
io.github.vpatser1/mcp-api-doc-generator is listed in the public MCP registry as io.github.vpatser1/mcp-api-doc-generator. Generate OpenAPI 3.1 specs, endpoint docs, TypeScript SDKs, and test suites from code. This page covers its npm package (mcp-api-doc-generator).
Is the io.github.vpatser1/mcp-api-doc-generator server safe to use?
io.github.vpatser1/mcp-api-doc-generator scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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.vpatser1/mcp-api-doc-generator server expose?
io.github.vpatser1/mcp-api-doc-generator exposes 5 tools: generate_openapi, document_endpoint, generate_sdk, validate_api, generate_tests. Their descriptions and schemas cost roughly 538 tokens of context every time the server is loaded.
Is the io.github.vpatser1/mcp-api-doc-generator server still maintained?
io.github.vpatser1/mcp-api-doc-generator is still listed as active in the MCP registry. We last reached this channel on 21 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.vpatser1/mcp-api-doc-generator server under?
io.github.vpatser1/mcp-api-doc-generator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.vpatser1/mcp-api-doc-generator server?
VerifyMCP ran 15 checks on io.github.vpatser1/mcp-api-doc-generator, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.vpatser1/mcp-api-doc-generator: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.