Data-grounded sprint retro
NPM · RETRO-MCP
Data-grounded sprint retrospectives from your Jira, GitHub, and Slack activity.
Available components
Last scanned (3 hours ago)
Scores higher than 66% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. 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 140 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 654 tokens (~109/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.93 functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 18 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
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/retro-mcp@0.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
action_item_review Action Item Review ~148
Close the loop on last retro's action items. Give the previous retro's action items and it attaches THIS sprint's relevant data to each, so the team can see what actually moved. Reviewing prior actions is the single proven lever on retro follow-through. It shows evidence only and lets you judge what counts as done.
| Name | Type | Req | Description |
|---|---|---|---|
| boardId | integer | – | Board id. Optional when the account has a single board, or set JIRA_BOARD_ID. |
| previousActions | array | – | Last retro's action items, one per entry. Omit in demo mode to use sample items. |
| sprintId | integer | – | Sprint id to reflect on. Optional: defaults to the most recently closed sprint. |
No output schema declared.
No examples provided.
discussion_prompts Discussion Prompts ~108
Open questions for the retro board, each grounded in a real anomaly from the closed sprint (a reopened ticket, mid-sprint scope, a slow review, a revert, a blocker). Questions to start the conversation, not verdicts that end it.
| Name | Type | Req | Description |
|---|---|---|---|
| boardId | integer | – | Board id. Optional when the account has a single board, or set JIRA_BOARD_ID. |
| sprintId | integer | – | Sprint id to reflect on. Optional: defaults to the most recently closed sprint. |
No output schema declared.
No examples provided.
list_sources List Sources ~55
Show which data sources are configured (Jira, plus optional GitHub and Slack enrichment), or that the server is running on a synthetic demo sprint. Does not hit the network; run the server with --check to verify live connections.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
retro_brief Retro Brief ~120
Generate a data-grounded sprint retrospective for the most recently closed sprint: What went well, What did not, Action items, and Discussion prompts. Every line is backed by a metric, ticket, PR, or Slack thread, framed around the process not individuals. Recurring themes across recent sprints are flagged.
| Name | Type | Req | Description |
|---|---|---|---|
| boardId | integer | – | Board id. Optional when the account has a single board, or set JIRA_BOARD_ID. |
| sprintId | integer | – | Sprint id to reflect on. Optional: defaults to the most recently closed sprint. |
No output schema declared.
No examples provided.
retro_metrics Retro Metrics ~118
The hard numbers behind the retro for the closed sprint: completion, mid-sprint scope change, carryover, reopens, average cycle time vs the prior sprint, velocity, PR review latency, reverts and hotfixes, and flagged Slack threads. This is the evidence base the brief draws from.
| Name | Type | Req | Description |
|---|---|---|---|
| boardId | integer | – | Board id. Optional when the account has a single board, or set JIRA_BOARD_ID. |
| sprintId | integer | – | Sprint id to reflect on. Optional: defaults to the most recently closed sprint. |
No output schema declared.
No examples provided.
sprint_compare Sprint Compare ~105
Compare the closed sprint against the one before it (completion, scope, carryover, reopens, cycle time, velocity), and list the problem themes that recur across recent sprints. Use it to tell a one-off from a pattern.
| Name | Type | Req | Description |
|---|---|---|---|
| boardId | integer | – | Board id. Optional when the account has a single board, or set JIRA_BOARD_ID. |
| sprintId | integer | – | Sprint id to reflect on. Optional: defaults to the most recently closed sprint. |
No output schema declared.
No examples provided.
How do I install the Data-grounded sprint retro MCP server?
Data-grounded sprint retro runs locally as an npm package, launched with npx -y retro-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 · retro-mcp
claude mcp add sathvic-kollu-retro-mcp -- npx -y retro-mcp
What is the Data-grounded sprint retro MCP server?
Data-grounded sprint retro is an MCP server listed in the public MCP registry as io.github.sathvic-kollu/retro-mcp. Data-grounded sprint retrospectives from your Jira, GitHub, and Slack activity. This page covers its npm package (retro-mcp).
Is the Data-grounded sprint retro MCP server safe to use?
Data-grounded sprint retro scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 Data-grounded sprint retro MCP server expose?
Data-grounded sprint retro exposes 6 tools: retro_brief, retro_metrics, discussion_prompts, action_item_review, sprint_compare, list_sources. Their descriptions and schemas cost roughly 654 tokens of context every time the server is loaded.
Is the Data-grounded sprint retro MCP server still maintained?
Data-grounded sprint retro 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 Data-grounded sprint retro MCP server under?
Data-grounded sprint retro declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.