# io.github.rbsoftwaresystems/draftlytic-mcp (npm · draftlytic-mcp)

Offline MCP server for planning structured project specs — validate, render, and checklist tools.

- Trust score: 69/100 (medium)
- Change this week: +18
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `draftlytic-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/rbsoftwaresystems-draftlytic-mcp/draftlytic-mcp.md), [page](https://verifymcp.io/servers/rbsoftwaresystems-draftlytic-mcp/draftlytic-mcp)

## Channel facts

- Registry: `npm`
- Package: `draftlytic-mcp`
- Version: `0.4.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 25 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 960 tokens (~240/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add rbsoftwaresystems-draftlytic-mcp -- npx -y draftlytic-mcp
```

### Codex

```bash
codex mcp add rbsoftwaresystems-draftlytic-mcp -- npx -y draftlytic-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rbsoftwaresystems-draftlytic-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "draftlytic-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rbsoftwaresystems-draftlytic-mcp --command npx --arg -y --arg draftlytic-mcp
```

### Hermes

```yaml
mcp_servers:
  rbsoftwaresystems-draftlytic-mcp:
    command: "npx"
    args: ["-y", "draftlytic-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "rbsoftwaresystems-draftlytic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "draftlytic-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 68, +44)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] License: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 24, −9)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 33, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 51)

First indexed and scored.

## MCP tools (4)

### `validate_spec` (~190 tokens)

Validate spec

Validate a project spec against the schema and return structured issues. A project spec: name, overview, target_audience, platforms[], tech_stack[], features[] ({title, description, priority: must-have|nice-to-have|future, acceptance_criteria?[]}), screens[]? ({name, purpose}), data_model[]? ({entity, fields[]: {name, type, notes?}}), constraints[]?, non_goals[]?, revenue_model?. Checks for missing/empty required sections, placeholder text (e.g. "TBD", "lorem ipsum", "fixme"), and features without a priority — all reported as errors. Also returns non-blocking quality hints, e.g. "none of your must-have features have acceptance_criteria" or "no non_goals listed".

Input parameters:

- `spec` (object, required): The spec object to validate, as a JSON value (not a JSON string).

### `render_prd` (~194 tokens)

Render PRD

Render a project spec into a deterministic, Draftlytic-style Markdown PRD. A project spec: name, overview, target_audience, platforms[], tech_stack[], features[] ({title, description, priority: must-have|nice-to-have|future, acceptance_criteria?[]}), screens[]? ({name, purpose}), data_model[]? ({entity, fields[]: {name, type, notes?}}), constraints[]?, non_goals[]?, revenue_model?. Output includes: title, overview, target audience, platforms, tech stack, features grouped by priority (must-have / nice-to-have / future) with acceptance-criteria checklists, screens & navigation, data model tables, constraints, and non-goals. Run validate_spec first — this tool renders whatever it's given, even an incomplete spec.

Input parameters:

- `spec` (object, required): The spec object to render, as a JSON value (not a JSON string).

### `spec_checklist` (~171 tokens)

Spec planning checklist

Return a planning checklist grouped by category (platform, tech stack, target audience, features, competitors, revenue, constraints, data model, notifications, external services, design & UX), each with 2-4 concrete questions. Use this to interview the user before drafting a spec — you don't need to ask every question, just enough per category to fill in the schema meaningfully. Each question is an object: `prompt` is the question text; when it also has `options` (a short list of suggested answers), present it as a selectable choice question rather than asking the user to type — with `multiSelect: true`, let them pick several. Always leave a free-text escape so the user can answer in their own words; questions with no `options` are open-ended and stay free-text.

### `open_in_draftlytic` (~167 tokens)

Open in Draftlytic

Build a link that opens this idea in the full Draftlytic app (free account, no card), which runs its own guided flow: AI-tailored questions, full project generation, an editable structured spec, and PRD export (plus scan-for-gaps, logo drafts, and GitHub push on paid plans). Pass either the spec drafted here (it gets compressed into a starting brief) or a plain-text idea. Show the returned URL to the user as a clickable link — this tool only builds it; nothing is sent anywhere.

Input parameters:

- `idea` (string): Plain-text idea to hand off when there is no spec yet.
- `spec` (object): A spec object (may be partial) to compress into the handoff brief. Takes precedence over `idea`.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/rbsoftwaresystems-draftlytic-mcp/draftlytic-mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 24
- 2026-07-31: 33
- 2026-07-30: 51
- 2026-07-28: 51
- 2026-07-27: 51

## Links

- npm package: https://www.npmjs.com/package/draftlytic-mcp
- Socket report: https://socket.dev/npm/package/draftlytic-mcp
- Repository: https://github.com/rbsoftwaresystems/draftlytic-mcp
- Changelog RSS feed: https://verifymcp.io/servers/rbsoftwaresystems-draftlytic-mcp/draftlytic-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/rbsoftwaresystems-draftlytic-mcp/draftlytic-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/rbsoftwaresystems-draftlytic-mcp/draftlytic-mcp