Data-grounded sprint retro
NPM · RETRO-MCP · SCANNED AUG 3
Data-grounded sprint retrospectives from your Jira, GitHub, and Slack activity.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 46 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · retro-mcp
claude mcp add sathvic-kollu-retro-mcp -- npx -y retro-mcp
codex mcp add sathvic-kollu-retro-mcp -- npx -y retro-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sathvic-kollu-retro-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"retro-mcp"
],
"enabled": true
}
}
} openclaw mcp add sathvic-kollu-retro-mcp --command npx --arg -y --arg retro-mcp
mcp_servers:
sathvic-kollu-retro-mcp:
command: "npx"
args: ["-y", "retro-mcp"] {
"mcpServers": {
"sathvic-kollu-retro-mcp": {
"command": "npx",
"args": [
"-y",
"retro-mcp"
]
}
}
} 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.
- 2 Aug 26 +64
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: unverified → fail ▼ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Stability: unverified → 0.20 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Jul 26 −23
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.