# Data-grounded sprint retro (npm · retro-mcp)

Data-grounded sprint retrospectives from your Jira, GitHub, and Slack activity.

- Trust score: 68/100 (medium)
- Change this week: +22
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- npm · `retro-mcp`: 68/100 (this document), [markdown](https://verifymcp.io/servers/sathvic-kollu-retro-mcp/retro-mcp.md), [page](https://verifymcp.io/servers/sathvic-kollu-retro-mcp/retro-mcp)

## Channel facts

- Registry: `npm`
- Package: `retro-mcp`
- Version: `0.1.0`
- 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-08-04.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **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 (MIT).
  - Actively maintained (last published 47 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 654 tokens (~109/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add sathvic-kollu-retro-mcp -- npx -y retro-mcp
```

### Codex

```bash
codex mcp add sathvic-kollu-retro-mcp -- npx -y retro-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add sathvic-kollu-retro-mcp --command npx --arg -y --arg retro-mcp
```

### Hermes

```yaml
mcp_servers:
  sathvic-kollu-retro-mcp:
    command: "npx"
    args: ["-y", "retro-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "sathvic-kollu-retro-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "retro-mcp"
      ]
    }
  }
}
```

## 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-08-04 (score 68, −1)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail

### 2026-08-02 (score 69, +64)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 5, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-07-31 (score 5, −23)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 28, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (6)

### `retro_brief` (~120 tokens)

Retro Brief

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.

Input parameters:

- `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.

### `retro_metrics` (~118 tokens)

Retro Metrics

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.

Input parameters:

- `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.

### `discussion_prompts` (~108 tokens)

Discussion Prompts

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.

Input parameters:

- `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.

### `action_item_review` (~148 tokens)

Action Item Review

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.

Input parameters:

- `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.

### `sprint_compare` (~105 tokens)

Sprint Compare

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.

Input parameters:

- `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.

### `list_sources` (~55 tokens)

List Sources

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.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/sathvic-kollu-retro-mcp/retro-mcp#diagnostics

## Score history

- 2026-08-04: 68
- 2026-08-03: 69
- 2026-08-02: 69
- 2026-08-01: 5
- 2026-07-31: 5
- 2026-07-30: 28
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/retro-mcp
- Socket report: https://socket.dev/npm/package/retro-mcp
- Repository: https://github.com/sathvic-kollu/retro-mcp
- Changelog RSS feed: https://verifymcp.io/servers/sathvic-kollu-retro-mcp/retro-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/sathvic-kollu-retro-mcp/retro-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/sathvic-kollu-retro-mcp/retro-mcp