Yeti
NPM · YETI-MCP
Product design with Claude: phases, requirements, user stories, RICE, flows, dashboard, Jira.
Available components
Last scanned (17 hours ago)
Scores higher than 41% of npm servers
Category Project Management
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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2164 tokens (~61/item across 35 items; 35 tools + 0 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 Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 36% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_requirement" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 35 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.
- 4 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.
- 2 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
- Security disclosure: fail → pass ▲ functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −12
- Malware scan: pass → unverified ▼ security
- Schema quality: 1940 → 2164 ▼ functional
- Stability: unverified → 0.20 ▲ functional
- Package version: 1.0.3 → 1.1.0 functional
- 26 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- 24 Oct 26 50
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 4 Nov 2026 · Analysed npm/yeti-mcp@1.1.0
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
add_decision ~97
Record a design decision for a project: what was chosen, why, and which alternatives were rejected. Decisions are kept with the project, so the reasons outlive the chat.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | string | – | What was considered and rejected |
| decision | string | yes | What was chosen |
| projectId | integer | yes | – |
| reason | string | yes | Why it was chosen |
| title | string | yes | Short name of the decision |
No output schema declared.
No examples provided.
add_requirement ~76
Record a product requirement with a MoSCoW priority (must, should, could, wont).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What the system must do and why |
| priority | string | – | – |
| projectId | integer | – | Id of the project to link this item to |
| title | string | yes | Short requirement title |
No output schema declared.
No examples provided.
add_user_story ~126
Create a user story in the format 'As a <persona> I want <goal> so that <benefit>', with acceptance criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | array | yes | Verifiable conditions that define done |
| benefit | string | yes | Why they want it |
| goal | string | yes | What they want to do |
| persona | string | yes | Who uses the feature, e.g. 'craftsman' |
| projectId | integer | – | Id of the project to link this item to |
| requirementIds | array | – | Ids of the requirements this story covers |
No output schema declared.
No examples provided.
advance_phase ~61
Move to the next phase. In 'strict' mode, it lists what is missing and does not advance. In 'free' mode, it advances and reports what was skipped. After 'verification' it closes the project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
archive_project ~44
Archive or unarchive a project. Archived projects are hidden from list_projects by default. Nothing is deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
create_project ~107
Create a design project. It starts in the 'discovery' phase: problem, users and goal are required. Mode 'strict' (default) blocks advancing until each phase is complete; 'free' allows advancing and reports what was skipped.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | What the user or business should achieve |
| mode | string | – | – |
| name | string | yes | – |
| problem | string | yes | The problem it solves |
| users | string | yes | Who it is for |
No output schema declared.
No examples provided.
create_project_from_template ~66
Create a project from a starter template. It starts in discovery with its requirements and user stories open, linked to each other. Adapt them afterwards with the usual tools.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Project name; defaults to the template name |
| templateId | string | yes | – |
No output schema declared.
No examples provided.
delete_flow ~41
Delete one saved flow diagram from a project, by the index shown by list_flows.
| Name | Type | Req | Description |
|---|---|---|---|
| index | integer | yes | – |
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
delete_project ~59
Permanently delete a project with its requirements and user stories. Requires confirm: true. This cannot be undone; issues already created in Jira are not touched.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true to delete |
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
delete_requirement ~35
Delete a requirement. It is also removed from the requirementIds of any user story that covered it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
delete_user_story ~21
Delete a user story.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
duplicate_project ~63
Create a new project from an existing one, copying its requirements and user stories as open items. Useful as a template for a new client or product. Statuses and RICE scores are not copied.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
export_backlog ~58
Export a project backlog as Markdown or CSV: requirements (most important first) and user stories.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| projectId | integer | yes | – |
| save | boolean | – | Also write the file to data/exports/ |
No output schema declared.
No examples provided.
export_dashboard ~64
Write a read-only HTML dashboard to data/exports/dashboard.html: phases, what is missing, musts covered by stories, RICE scores and flow diagrams. Open the file in a browser.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | integer | – | Id of the project to link this item to |
No output schema declared.
No examples provided.
get_project ~34
Show a project's status: current phase, what is missing to advance, and linked items.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
import_requirements ~76
Import requirements and user stories from CSV text, in the format produced by export_backlog. Requirement rows need type and title; story rows need persona, goal, benefit and criteria (separated by ' | '). Story-to-requirement links are not restored.
| Name | Type | Req | Description |
|---|---|---|---|
| csv | string | yes | – |
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
list_decisions ~29
List the design decisions recorded for a project, oldest first.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
list_flows ~39
List the flow diagrams saved in a project, with their index. Use the index to refer to a diagram.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
list_projects ~59
List projects with their id, name, phase and status. Use it to find a projectId.
| Name | Type | Req | Description |
|---|---|---|---|
| includeArchived | boolean | – | Set to true to also list archived projects |
| includeClosed | boolean | – | Set to false to hide closed projects |
No output schema declared.
No examples provided.
list_requirements ~56
List requirements, optionally filtered by priority, status and project. Most important first.
| Name | Type | Req | Description |
|---|---|---|---|
| priority | string | – | – |
| projectId | integer | – | Id of the project to link this item to |
| status | string | – | – |
No output schema declared.
No examples provided.
list_stories ~53
List user stories, optionally for one project, with their ids, criteria state and Jira key. Use it to find a storyId.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | integer | – | Id of the project to link this item to |
No output schema declared.
No examples provided.
list_templates ~32
List the starter project templates: a marketplace MVP and a customer self-service portal. Use one with create_project_from_template.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
map_user_flow ~105
Generate a Mermaid flowchart from a list of steps. Steps are linked in order; a decision (diamond) gets a 'Yes' edge to the next step, or to 'yes' if set, and a 'No' edge to 'no' if set. With projectId, saves the diagram to the project.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| projectId | integer | – | Id of the project to link this item to |
| steps | array | yes | – |
No output schema declared.
No examples provided.
open_dashboard ~70
Start the local, read-only Yeti dashboard and return its address (http://127.0.0.1:...). It shows phases, what is missing, musts and their stories, RICE and flows, and refreshes by itself. It runs on this computer only, while Yeti runs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prioritize_rice ~68
Compute RICE scores (Reach × Impact × Confidence ÷ Effort) for a list of ideas and sort them. With projectId, saves the result to the project.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| projectId | integer | – | Id of the project to link this item to |
No output schema declared.
No examples provided.
project_summary ~52
Summarise a project's progress: requirements by priority and status, story coverage of musts, acceptance criteria done, RICE leader, Jira links and what is missing to close.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
push_to_jira ~130
Create Jira issues for a project: one Task per requirement and one Story per user story. Items already sent are skipped. With update: true, also refreshes the issues already linked. dryRun (default true) only lists what would be sent.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | – |
| limit | integer | – | Send at most this many new issues; useful to test with one |
| projectId | integer | yes | – |
| projectKey | string | yes | Jira project key, e.g. PROJ |
| update | boolean | – | Also update issues already linked to a requirement or story |
No output schema declared.
No examples provided.
search_items ~51
Search requirements and user stories by text (case-insensitive). Optionally limit to one project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | integer | – | Id of the project to link this item to |
| query | string | yes | – |
No output schema declared.
No examples provided.
set_criterion_status ~60
Mark one acceptance criterion of a user story as done or not done. The index is 0-based, in the order of the criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| done | boolean | yes | – |
| index | integer | yes | – |
| storyId | integer | yes | – |
No output schema declared.
No examples provided.
set_project_mode ~43
Change a project's mode: 'strict' or 'free'. Applies from the next phase change.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | yes | – |
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
set_requirement_status ~31
Mark a requirement as open or done.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
sync_from_jira ~56
Read the status of linked Jira issues and mark items done in Yeti when their Jira issue is done. Requirements become done; stories get all their criteria ticked. Read-only on Jira.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | integer | yes | – |
No output schema declared.
No examples provided.
update_project ~63
Change a project's name, problem, users or goal. Only the fields you pass are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | – |
| name | string | – | – |
| problem | string | – | – |
| projectId | integer | yes | – |
| users | string | – | – |
No output schema declared.
No examples provided.
update_requirement ~54
Change a requirement's title, description or priority. Only the fields you pass are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| id | integer | yes | – |
| priority | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
update_user_story ~85
Change a user story's persona, goal, benefit, linked requirements or acceptance criteria. Only the fields you pass change. Changing the criteria resets their done state.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | array | – | – |
| benefit | string | – | – |
| goal | string | – | – |
| id | integer | yes | – |
| persona | string | – | – |
| requirementIds | array | – | – |
No output schema declared.
No examples provided.
How do I install the Yeti MCP server?
Yeti runs locally as an npm package, launched with npx -y yeti-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · yeti-mcp
claude mcp add macorifice-yeti -- npx -y yeti-mcp
What is the Yeti MCP server?
Yeti is an MCP server listed in the public MCP registry as io.github.macorifice/yeti. Product design with Claude: phases, requirements, user stories, RICE, flows, dashboard, Jira. This page covers its npm package (yeti-mcp).
Is the Yeti MCP server safe to use?
Yeti scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Yeti MCP server expose?
Yeti exposes 35 tools: create_project, list_projects, update_requirement, delete_requirement, delete_user_story, and 30 more. Their descriptions and schemas cost roughly 2,164 tokens of context every time the server is loaded.
Is the Yeti MCP server still maintained?
Yeti is still listed as active in the MCP registry. We last reached this channel on 4 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 Yeti MCP server under?
Yeti declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.