io.github.AINative-Studio/ainative-prd-mcp
NPM · AINATIVE-PRD-MCP · SCANNED AUG 3
PRD Generator MCP — generate, validate, and manage Product Requirement Documents.
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 Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (108 of 109), 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 (108 of 109), 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 2 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 2045 tokens (~88/item across 23 items; 23 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 · ainative-prd-mcp
claude mcp add ainative-studio-ainative-prd-mcp -- npx -y ainative-prd-mcp
codex mcp add ainative-studio-ainative-prd-mcp -- npx -y ainative-prd-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ainative-studio-ainative-prd-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"ainative-prd-mcp"
],
"enabled": true
}
}
} openclaw mcp add ainative-studio-ainative-prd-mcp --command npx --arg -y --arg ainative-prd-mcp
mcp_servers:
ainative-studio-ainative-prd-mcp:
command: "npx"
args: ["-y", "ainative-prd-mcp"] {
"mcpServers": {
"ainative-studio-ainative-prd-mcp": {
"command": "npx",
"args": [
"-y",
"ainative-prd-mcp"
]
}
}
} 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 +43
- 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
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 21
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/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 108 packages
108 packages in the resolved dependency tree · 108 deprecated · 32 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.
prd_check_api_refs ~69
Verify that all API endpoint references in a PRD actually exist in the AINative OpenAPI spec. Catches typos and invalid paths.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | — | PRD content to check |
| prd_id | string | — | ID of a saved PRD to check |
No output schema declared.
No examples provided.
prd_create_template ~89
Create a custom PRD template. Stored persistently in ZeroDB so it survives across sessions.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Markdown template content with {{PLACEHOLDER}} variables |
| description | string | yes | What this template is for |
| name | string | yes | Template name (lowercase, hyphens allowed) |
| sections | array | — | List of section names in this template |
No output schema declared.
No examples provided.
prd_from_issue ~87
Generate a PRD from a GitHub issue. Fetches the issue title, body, labels, and comments, then expands them into a full PRD with AINative platform context.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_number | integer | yes | GitHub issue number |
| repo | string | — | GitHub repository (owner/repo format) |
| template | string | — | PRD template to use |
No output schema declared.
No examples provided.
prd_generate ~230
Generate a comprehensive Product Requirements Document (PRD) for an AINative feature, integration, or product. Uses AI with full AINative platform context — knows all services, APIs, SDKs, and architectural constraints. The PRD is automatically saved to ZeroMemory for cross-session recall.
| Name | Type | Req | Description |
|---|---|---|---|
| additional_context | string | — | Any additional context, links, or requirements |
| ainative_services | array | — | AINative services this feature will use (e.g., ["ZeroDB", "ZeroMemory", "Agent Cloud"]). If omitted, the generator will auto-detect relevant services. |
| constraints | array | — | Technical or business constraints |
| core_features | array | yes | List of core features to include |
| description | string | yes | Detailed description of what needs to be built |
| issue_number | integer | — | Optional GitHub issue number to link to |
| product_name | string | yes | Name of the product or feature |
| target_audience | string | yes | Who will use this product/feature |
| template | string | — | PRD template to use (default: standard) |
No output schema declared.
No examples provided.
prd_generate_section ~136
Generate or regenerate a single section of a PRD. Useful for iterative refinement — update just the Technical Architecture or User Stories without regenerating the entire document.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | — | Additional context for generating this section |
| description | string | — | Product description (required if no prd_id) |
| prd_id | string | — | ID of an existing saved PRD (from prd_save). If provided, the section will be generated in context of the full PRD. |
| product_name | string | — | Product name (required if no prd_id) |
| section_name | string | yes | Which section to generate |
No output schema declared.
No examples provided.
prd_get_api_catalog ~78
Get API endpoint details for a specific AINative service or category. Returns endpoint paths, methods, and descriptions from the OpenAPI catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | Service name (e.g., "ZeroDB", "ZeroMemory", "Agent Cloud") or API prefix (e.g., "/api/v1/zerodb") |
No output schema declared.
No examples provided.
prd_get_template ~52
Get a PRD template by name. Returns the full Markdown template with placeholder variables.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Template name (e.g., "standard", "ainative-feature", "agent-capability") |
No output schema declared.
No examples provided.
prd_history ~46
Get version history for a PRD, showing how it evolved over time. Returns unified diffs between versions.
| Name | Type | Req | Description |
|---|---|---|---|
| prd_id | string | yes | Artifact ID of the PRD |
No output schema declared.
No examples provided.
prd_list_services ~98
List all AINative products and services with descriptions, categories, API prefixes, SDKs, and pricing tiers. Use this before writing a PRD to understand what platform capabilities are available.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Filter by category (e.g., "Data Platform", "AI Inference", "Business", "Infrastructure") |
| verbose | boolean | — | Include full details including features, SDKs, and endpoints (default: false) |
No output schema declared.
No examples provided.
prd_list_templates ~56
List all available PRD templates (built-in and custom). Each template has a specific structure optimized for different types of products and features.
| Name | Type | Req | Description |
|---|---|---|---|
| include_custom | boolean | — | Include custom templates stored in ZeroDB (default: true) |
No output schema declared.
No examples provided.
prd_load ~55
Load a saved PRD by its artifact ID. Use at the start of a session to resume work on an existing PRD.
| Name | Type | Req | Description |
|---|---|---|---|
| prd_id | string | yes | Artifact ID returned by prd_save or prd_generate |
No output schema declared.
No examples provided.
prd_refine ~109
Refine an existing PRD based on feedback. Provide the PRD ID and feedback, and the AI will update the document while preserving version history.
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | string | yes | Feedback describing what needs to change (e.g., "Add more detail to user stories", "The API design should use WebSockets instead of polling") |
| prd_id | string | yes | ID of the saved PRD to refine |
| sections_to_update | array | — | Optional: limit refinement to specific sections |
No output schema declared.
No examples provided.
prd_render_template ~73
Render a template with variable substitution (no AI, pure placeholder replacement). Fast and deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| template_name | string | yes | Template to render |
| variables | object | yes | Key-value pairs for placeholder substitution (e.g., {"PRODUCT_NAME": "My Feature", "TARGET_AUDIENCE": "Developers"}) |
No output schema declared.
No examples provided.
prd_save ~112
Save a PRD to ZeroDB as a persistent plan artifact. Returns an ID you can use to load, update, or search for it in future sessions. Version history is tracked automatically on every update.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Full PRD content in Markdown |
| tags | array | — | Tags for categorization (e.g., ["billing", "agent-cloud", "q3-2026"]) |
| title | string | yes | PRD title (e.g., "PRD: Agent Cloud Billing") |
No output schema declared.
No examples provided.
prd_score ~63
Score a PRD completeness from 0-100 based on section coverage, content quality, and AINative integration depth.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | — | PRD content in Markdown |
| prd_id | string | — | ID of a saved PRD to score |
No output schema declared.
No examples provided.
prd_search ~83
Semantic search across all saved PRDs. Find PRDs by topic, service name, feature description, or any natural language query.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Maximum results to return |
| query | string | yes | Natural language search query (e.g., "PRDs about agent billing", "streaming video features") |
| tags | array | — | Filter by tags |
No output schema declared.
No examples provided.
prd_suggest_stack ~94
Given a set of requirements, suggest which AINative services, APIs, and SDKs to use. Returns a recommended technology stack with justifications.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | — | Technical constraints (e.g., "must work offline", "real-time updates needed") |
| features | array | — | List of required features/capabilities |
| requirements | string | yes | Natural language description of what you need to build |
No output schema declared.
No examples provided.
prd_validate ~99
Validate a PRD against quality rules and AINative architectural constraints. Checks for required sections, content completeness, AINative service references, and architecture compliance.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | — | PRD content in Markdown (provide directly or use prd_id) |
| prd_id | string | — | ID of a saved PRD to validate |
| strict | boolean | — | Strict mode: also check AINative-specific rules (default: true) |
No output schema declared.
No examples provided.
skill_get ~90
Get the full content of a skill by slug or name, including its SKILL.md body and (optionally) all reference files. Use this to load a skill before doing the work it describes.
| Name | Type | Req | Description |
|---|---|---|---|
| skill | string | yes | Skill slug or name (e.g., "agentic-platform-builder") |
| with_references | boolean | — | Also fetch the full content of every reference file (default: false) |
No output schema declared.
No examples provided.
skill_get_reference ~78
Get a single reference file for a skill (e.g., "references/testing-patterns.md"). Load reference files on demand when the SKILL.md says to.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | Reference file path, e.g. "references/agent-patterns.md" or "agent-patterns.md" |
| skill | string | yes | Skill slug |
No output schema declared.
No examples provided.
skill_list ~95
List all Agent Skills available in the skills repo (the8genc/ai-8gent-skills by default). Each entry includes the skill name, slug, description (with trigger phrases), and its reference files. Skills are pulled live from GitHub. Call this first to discover which skills exist before applying one.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | — | Bypass the in-memory cache and re-fetch from GitHub (default: false) |
No output schema declared.
No examples provided.
skill_search ~80
Semantic search across all skills to find the right one for a task. Queries the ZeroDB mirror when available (run skill_sync first), otherwise falls back to keyword matching over the live GitHub list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Max results |
| query | string | yes | Natural language description of the task (e.g., "automate my content workflow") |
No output schema declared.
No examples provided.
skill_sync ~73
Mirror skills from the GitHub repo into ZeroDB so they can be semantically searched and served offline. GitHub remains the source of truth — this refreshes the cache. Sync all skills, or one by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| skill | string | — | Optional: sync only this skill slug. Omit to sync all skills. |
No output schema declared.
No examples provided.