# Policyseed (npm · policyseed)

Draft SOC 2 policies from your AI assistant, via MCP

- Trust score: 78/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `policyseed`: 78/100 (this document), [markdown](https://verifymcp.io/servers/odedmoshe-policyseed/policyseed.md), [page](https://verifymcp.io/servers/odedmoshe-policyseed/policyseed)

## Channel facts

- Registry: `npm`
- Package: `policyseed`
- Version: `1.1.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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **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 (Apache-2.0).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 87/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).
  - Tool/resource definitions use about 1871 tokens (~69/item across 27 items; 5 tools + 22 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Policyseed MCP server?

Policyseed runs locally as an npm package, launched with npx -y policyseed. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add odedmoshe-policyseed -- npx -y policyseed
```

### Cursor

```json
{
  "mcpServers": {
    "odedmoshe-policyseed": {
      "command": "npx",
      "args": [
        "-y",
        "policyseed"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "odedmoshe-policyseed": {
      "command": "npx",
      "args": [
        "-y",
        "policyseed"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add odedmoshe-policyseed -- npx -y policyseed
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add odedmoshe-policyseed --command npx --arg -y --arg policyseed
```

### Hermes

```yaml
mcp_servers:
  odedmoshe-policyseed:
    command: "npx"
    args: ["-y", "policyseed"]
```

### Netclaw

```json
{
  "McpServers": {
    "odedmoshe-policyseed": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "policyseed"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add odedmoshe-policyseed -t stdio -c npx -a -y policyseed
```

### Other

```json
{
  "mcpServers": {
    "odedmoshe-policyseed": {
      "command": "npx",
      "args": [
        "-y",
        "policyseed"
      ]
    }
  }
}
```

## 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-11-05 (score 78, +1)

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

### 2026-11-03 (score 77, +1)

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

### 2026-11-01 (score 76, +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-10-30 (score 75, +1)

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

### 2026-10-27 (score 74, +1)

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

### 2026-10-25 (score 73)

First indexed and scored.

## MCP tools (5)

### `list_policies` (~79 tokens)

List SOC 2 policies

List the 22 SOC 2 policy templates Policyseed can render: id, slug, title, one-line summary, owner role, output file name and the SOC 2 Trust Services Criteria each covers. Use the slug with render_policy. Every policy shares one review cadence, set by the intake's review_cadence field (Annual by default).

### `intake_questions` (~89 tokens)

Get intake questions

Return every intake field the policy renderer needs, with type, whether it is required, allowed values, length limits, default and a description. Call this first, then interview the user: ask for the required fields (company, product, security_owner, approver, incident_contact) and confirm or change the defaults (cloud, identity provider, data types, etc.) before calling render_policy or render_all.

### `render_policy` (~150 tokens)

Render one policy

Render a single SOC 2 policy as Markdown from the company intake, exactly as `policyseed build` writes it (company-titled H1, 9 standard sections, revision history). Returns the Markdown text; suggest saving it as the file_name shown by list_policies. Invalid intake values are reported back so you can fix them.

Input parameters:

- `intake` (object, required): The company intake. Only company, product, security_owner, approver and incident_contact are required; any omitted field takes its default (see intake_questions; effective_date defaults to today).
- `slug` (string, required): Policy slug from list_policies, e.g. "access-control-policy". The policy id ("P03") also works.

### `render_all` (~163 tokens)

Render all policies

Render all 22 SOC 2 policies (or the subset named in `slugs`) as Markdown from the company intake. Output is large (roughly 250 KB for all 22): the first content item is an index, then one item per policy starting with an HTML comment naming its file, e.g. <!-- file: 03-access-control-policy.md -->. Prefer render_policy when the user only needs one or two documents.

Input parameters:

- `intake` (object, required): The company intake. Only company, product, security_owner, approver and incident_contact are required; any omitted field takes its default (see intake_questions; effective_date defaults to today).
- `slugs` (array): Optional subset of policy slugs to render. Omit to render all 22.

### `check_reviews` (~222 tokens)

Check policy review dates

Run the same logic as `policyseed check`: read previously rendered policies (NN-<slug>.md files) and report which are overdue for their periodic review, based on the last date in each policy's revision history and the intake's review_cadence (Annual 365d, Semi-annual 182d, Quarterly 91d). Paths are on the machine running this server; pass `directory` as an absolute path to the project, since the server's working directory may not be the user's project.

Input parameters:

- `directory` (string): Project directory containing intake.yaml and policies/. Defaults to the server's working directory.
- `intake` (object): Optional inline intake instead of reading intake.yaml; only review_cadence and effective_date are used.
- `intake_path` (string): Path to intake.yaml. Relative paths resolve against `directory`. Default "intake.yaml". Ignored if `intake` is given.
- `policies_dir` (string): Directory of rendered policy .md files. Relative paths resolve against `directory`. Default "policies".

## Diagnostics

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

## Score history

- 2026-11-05: 78
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 74
- 2026-10-28: 74
- 2026-10-27: 74
- 2026-10-26: 73
- 2026-10-25: 73

## Common questions

### What is the Policyseed MCP server?

Policyseed is an MCP server listed in the public MCP registry as io.github.odedmoshe/policyseed. Draft SOC 2 policies from your AI assistant, via MCP. This page covers its npm package (policyseed).

### Is the Policyseed MCP server safe to use?

Policyseed scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting 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 Policyseed MCP server expose?

Policyseed exposes 5 tools: list_policies, intake_questions, render_policy, render_all, check_reviews. Their descriptions and schemas cost roughly 703 tokens of context every time the server is loaded.

### Is the Policyseed MCP server still maintained?

Policyseed 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 Policyseed MCP server under?

Policyseed declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/policyseed
- Socket report: https://socket.dev/npm/package/policyseed
- Repository: https://github.com/odedmoshe/policyseed
- Website: https://policyseed.io/integrations
- Changelog RSS feed: https://verifymcp.io/servers/odedmoshe-policyseed/policyseed.xml
- Changelog JSON feed: https://verifymcp.io/servers/odedmoshe-policyseed/policyseed.json
- HTML version of this page: https://verifymcp.io/servers/odedmoshe-policyseed/policyseed