Policyseed
NPM · POLICYSEED
Draft SOC 2 policies from your AI assistant, via MCP
Available components
Last scanned (2 hours ago)
Scores higher than 58% of npm servers
Category Security
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 (Apache-2.0).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1871 tokens (~69/item across 27 items; 5 tools + 22 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 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
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 73
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 5 Nov 2026 · Analysed npm/policyseed@1.1.1
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 →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
check_reviews Check policy review dates ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
intake_questions Get intake questions ~89
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_policies List SOC 2 policies ~79
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
render_all Render all policies ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| intake | object | yes | 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. |
No output schema declared.
No examples provided.
render_policy Render one policy ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| intake | object | yes | 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 | yes | Policy slug from list_policies, e.g. "access-control-policy". The policy id ("P03") also works. |
No output schema declared.
No examples provided.
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.
npm · policyseed
claude mcp add odedmoshe-policyseed -- npx -y policyseed
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.