# com.qretro/retro (remote · mcp.qretro.com)

QRetro retrospectives and planning poker over MCP: boards, action items, poker games, estimates.

- Trust score: 80/100 (high trust)
- Change this week: +56
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.qretro.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-qretro-retro/mcp.md), [page](https://verifymcp.io/servers/com-qretro-retro/mcp)

## Channel facts

- Endpoint: `https://mcp.qretro.com`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-03.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3489 tokens (~120/item across 29 items; 29 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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 --transport http com-qretro-retro https://mcp.qretro.com/
```

### Codex

```toml
[mcp_servers.com-qretro-retro]
url = "https://mcp.qretro.com/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-qretro-retro": {
      "type": "remote",
      "url": "https://mcp.qretro.com/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-qretro-retro --url https://mcp.qretro.com/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-qretro-retro:
    url: "https://mcp.qretro.com/"
```

### Other

```json
{
  "mcpServers": {
    "com-qretro-retro": {
      "type": "http",
      "url": "https://mcp.qretro.com/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-03 (score 80, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-02 (score 79, +41)

- [security improvement] Transport: unverified → pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail

### 2026-07-31 (score 38, +14)

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

### 2026-07-30 (score 24, 0)

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

### 2026-07-27 (score 24, +3)

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

### 2026-07-26 (score 21)

First indexed and scored.

## MCP tools (29)

### `retro.teams.list` (~47 tokens)

List Teams Tool

Returns the list of teams the user belongs to. boards_count is the total number of boards in a team, finished and unfinished alike — use retro.boards.list to tell them apart.

### `retro.team.members.list` (~127 tokens)

List Team Members Tool

Returns the members of a team with their id, name and role (owner, admin, facilitator, member). Use the id as assign_to in retro.actions.create, retro.actions.update and retro.board.suggested_actions.promote. This is the team roster, the same one people see in team settings — it says nothing about who wrote which card. Pass team_id when several teams are available; with a single team it can be omitted.

Input parameters:

- `team_id` (string): Team to list members for. Required when more than one team is available — call retro.teams.list first.

### `retro.boards.list` (~168 tokens)

List Boards Tool

Returns retrospectives (boards) of a team, newest first. Unfinished boards are included unless finished_only is set — otherwise check the is_finished flag. Filters by period via since/until. Pass team_id when several teams are available; with a single team it can be omitted.

Input parameters:

- `finished_only` (boolean): Return only finished retrospectives. Default: false, unfinished boards are included.
- `since` (string): Only boards created on or after this date (ISO 8601, for example 2026-01-01).
- `team_id` (string): Team to list boards for. Required when more than one team is available — call retro.teams.list first.
- `until` (string): Only boards created on or before this date (ISO 8601).

### `retro.actions.list` (~182 tokens)

List Actions Tool

Returns action items across all retrospectives at once — the answer to "what did we agree on and never finish". Covers every team available unless team_id narrows it down; filters by status, assignee and date. Use this instead of walking boards one by one with retro.board.actions.list.

Input parameters:

- `assignee` (string): Filter by assignee name, partial match.
- `limit` (integer): How many items to return, newest first. Default 50, maximum 200. The total field always reports the full count.
- `since` (string): Only items created on or after this date (ISO 8601, for example 2026-01-01).
- `status` (string): open (default), completed or all.
- `team_id` (string): Narrow the search to one team. By default every available team is included.

### `retro.board.messages.list` (~71 tokens)

Get Board Messages Tool

Returns all participant messages (cards) for a retrospective board, organized by template columns (e.g. "What went well", "What didn't go well"). Includes text, sentiment, category, grouping, and vote counts.

Input parameters:

- `board_id` (string, required): The ID of the board to get messages for.

### `retro.board.messages.update` (~53 tokens)

Update Message Tool

Updates the text of an existing board message created by the current MCP user.

Input parameters:

- `message_id` (string, required): The ID of the message to update.
- `text` (string, required): New text content for the message.

### `retro.board.messages.delete_own` (~68 tokens)

Delete Own Message Tool

Deletes a single board message. Access is strictly governed by API policies: users can delete their own messages, or any message if they have board update rights (requires mcp:write scope for the latter).

Input parameters:

- `message_id` (string, required): The ID of the message to delete.

### `retro.board.summary.get` (~61 tokens)

Get Board Summary Tool

Returns the summary of a retrospective with participant info and metadata. Works for unfinished boards too — summary is null until the retro is wrapped up, so check is_finished.

Input parameters:

- `board_id` (string, required): The ID of the board to get the summary for.

### `retro.board.actions.list` (~66 tokens)

Get Board Actions Tool

Returns action items from a retrospective board, including status, priority, assignee, and due date.

Input parameters:

- `board_id` (string, required): The ID of the board to get action items for.
- `include_completed` (boolean): Whether to include completed action items. Default: false.

### `retro.board.insights.list` (~54 tokens)

Get Board Insights Tool

Returns insights (clusters) and suggested actions for a retrospective board. Insights include topic clusters with sentiment, urgency, and category analysis.

Input parameters:

- `board_id` (string, required): The ID of the board to get insights for.

### `retro.board.health.get` (~86 tokens)

Get Board Health Tool

Returns the health check of a retrospective: score per category on a 0-10 scale, alignment between participants, turnout, and the same score across the previous retrospectives of the team. Returns health_check: null when the team did not run a health check on this board.

Input parameters:

- `board_id` (string, required): The ID of the board to get the health check report for.

### `retro.board.roti.get` (~60 tokens)

Get Board Roti Tool

Returns ROTI (Return on Time Invested) voting metrics for a retrospective board, including average score, distribution, and trend across previous retrospectives.

Input parameters:

- `board_id` (string, required): The ID of the board to get ROTI metrics for.

### `retro.boards.search` (~80 tokens)

Search Boards Tool

Search across retrospectives by keyword: board summaries, action items and participant cards. Cards hidden by private writing during an ongoing retro are excluded. Optionally filter by team.

Input parameters:

- `query` (string, required): Search query. Looks into board summaries, action items and participant cards.
- `team_id` (string): Optional: filter search to a specific team.

### `retro.actions.create` (~146 tokens)

Create Action Item Tool

Creates a new action item on a retrospective board. Requires mcp:write scope.

Input parameters:

- `assign_to` (string): User ID to assign the action item to — call retro.team.members.list to get it — or "me" to assign to the current user.
- `board_id` (string, required): The ID of the board to create the action item on.
- `due` (string): Due date in ISO 8601 format (e.g. 2025-03-15T00:00:00Z).
- `priority` (string): Priority: high, medium, or low. Default: medium.
- `text` (string, required): The text of the action item.

### `retro.actions.update` (~129 tokens)

Update Action Item Tool

Updates an existing action item: text, priority, due date, or assignee. Requires mcp:write scope.

Input parameters:

- `action_item_id` (string, required): The ID of the action item to update.
- `assign_to` (string): User ID to reassign to — call retro.team.members.list to get it — or "me" to assign to the current user.
- `due` (string): New due date in ISO 8601 format.
- `priority` (string): New priority: high, medium, or low.
- `text` (string): New text for the action item.

### `retro.actions.complete` (~42 tokens)

Complete Action Item Tool

Marks an action item as completed. Requires mcp:write scope.

Input parameters:

- `action_item_id` (string, required): The ID of the action item to mark as completed.

### `retro.board.suggested_actions.promote` (~147 tokens)

Promote Suggested Action Tool

Turns a pending suggested action from retro.board.insights.list into a real action item on the board and marks the suggestion accepted, keeping the wording and the link to its cluster. Requires mcp:write scope.

Input parameters:

- `assign_to` (string): User ID to assign the action item to — call retro.team.members.list to get it — or "me" to assign to the current user.
- `board_id` (string, required): The ID of the board the suggestion belongs to.
- `suggested_action_id` (string, required): The ID of the suggested action to promote, from suggested_actions in retro.board.insights.list. Only suggestions with status "pending" can be promoted.

### `retro.board.suggested_actions.reject` (~100 tokens)

Reject Suggested Action Tool

Rejects a pending suggested action from retro.board.insights.list: the suggestion moves to rejected and no action item is created. Requires mcp:write scope.

Input parameters:

- `board_id` (string, required): The ID of the board the suggestion belongs to.
- `suggested_action_id` (string, required): The ID of the suggested action to reject, from suggested_actions in retro.board.insights.list. Only suggestions with status "pending" can be rejected.

### `poker.sources.list` (~104 tokens)

List Poker Sources Tool

Returns the issue trackers connected to a team (Jira, Linear) and what each of them can do: search for tasks, list iterations (sprints, cycles), write estimates back. Call this first — the other poker tools depend on what is connected. An empty list means tasks can only be added manually with poker.game.tasks.add.

Input parameters:

- `team_id` (string): Team to inspect. Required when more than one team is available — call retro.teams.list first.

### `poker.iterations.list` (~171 tokens)

List Poker Iterations Tool

Returns the iterations of a connected issue tracker — Jira sprints (active and upcoming), and whatever a future tracker calls the same thing. Filter by name with query, for example "AFT 50". Pass the ref of the iteration you want to poker.game.tasks.import to pull its tasks into a game. Trackers without iteration support (currently Linear) return an empty list — search by text instead.

Input parameters:

- `query` (string): Filter iterations by name, for example "AFT 50". Omit to get all active and upcoming ones.
- `source` (string): Tracker to query, for example jira. Required only when the team has several trackers connected — see poker.sources.list.
- `team_id` (string): Team whose tracker is queried. Required when more than one team is available.

### `poker.games.list` (~99 tokens)

List Poker Games Tool

Returns the planning poker games of a team, newest first, with how many tasks each of them has and how many already carry an estimate. Personal games outside a team are not exposed over MCP.

Input parameters:

- `limit` (integer): How many games to return. Default: 20, maximum: 50.
- `team_id` (string): Team to list games for. Required when more than one team is available — call retro.teams.list first.

### `poker.game.get` (~59 tokens)

Get Poker Game Tool

Returns one planning poker game: its estimation scale, progress, the task currently on the table and the link participants use to join. Use poker.game.tasks.list for the tasks themselves.

Input parameters:

- `game_id` (string, required): The ID of the poker game.

### `poker.game.tasks.list` (~136 tokens)

List Poker Tasks Tool

Returns the tasks of a poker game with their estimate, individual votes, tracker key and link. needs_sync tells whether the agreed estimate still differs from the one stored in the tracker — feed those tasks to poker.game.task.sync. Filter with estimated to see what is done or what is left.

Input parameters:

- `estimated` (boolean): true — only tasks that already have an estimate, false — only tasks still to be estimated. Omit for all of them.
- `game_id` (string, required): The ID of the poker game.
- `limit` (integer): How many tasks to return. Default: 50, maximum: 100.

### `poker.games.create` (~154 tokens)

Create Poker Game Tool

Creates a planning poker game for a team and returns the link participants join with. Pick a ready-made scale — fibonacci, modified_fibonacci, tshirts, powers_of_two — or pass your own values in scale_values. Requires mcp:write scope.

Input parameters:

- `name` (string, required): Name of the game, for example the sprint it plans.
- `scale` (string): Estimation scale preset: fibonacci (default), modified_fibonacci, tshirts, powers_of_two.
- `scale_values` (array): Custom scale, for example ["1","2","3","5","?"]. Overrides scale when given.
- `team_id` (string): Team the game belongs to. Required when more than one team is available.

### `poker.game.tasks.add` (~90 tokens)

Add Poker Tasks Tool

Adds tasks to a poker game by hand — for work that lives outside an issue tracker, or when no tracker is connected. To pull tasks from Jira or Linear use poker.game.tasks.import instead. Requires mcp:write scope.

Input parameters:

- `game_id` (string, required): The ID of the poker game.
- `tasks` (array, required): Tasks to add: a list of objects with name and optional description.

### `poker.game.tasks.import` (~184 tokens)

Import Poker Tasks Tool

Pulls tasks from a connected issue tracker into a poker game. Give it either iteration_ref from poker.iterations.list to take a whole sprint, or query to search by text and issue key. Tasks already in the game are skipped. Only the team owner can change a game. Requires mcp:write scope.

Input parameters:

- `game_id` (string, required): The ID of the poker game to import into.
- `iteration_ref` (string): The ref of an iteration from poker.iterations.list — imports every task of that sprint.
- `limit` (integer): How many tasks to pull at most. Default: 50, maximum: 100.
- `query` (string): Text or issue key to search for, when importing without an iteration.
- `source` (string): Tracker to import from, for example jira. Required only when the team has several trackers connected.

### `poker.game.task.select` (~87 tokens)

Select Poker Task Tool

Puts a task on the table: everyone looking at the game sees it as the one being estimated right now. Only the team owner can change a game. Requires mcp:write scope.

Input parameters:

- `game_id` (string, required): The ID of the poker game.
- `task_id` (string, required): The ID of the task to put on the table — see poker.game.tasks.list.

### `poker.game.task.reveal` (~146 tokens)

Reveal Poker Task Tool

Reveals the cards of a task and computes its estimate from the votes cast — this is the only way an estimate appears, there is no way to set a number directly. Pass reveal=false to hide the cards again and drop the estimate, which also clears the votes for a re-vote. Only the team owner can change a game. Requires mcp:write scope.

Input parameters:

- `game_id` (string, required): The ID of the poker game.
- `reveal` (boolean): true (default) — reveal the cards and compute the estimate. false — hide them, clear the votes and the estimate.
- `task_id` (string, required): The ID of the task to reveal.

### `poker.game.task.sync` (~112 tokens)

Sync Poker Estimate Tool

Writes the agreed estimate back to the issue tracker — Jira story points, Linear estimate. Works only for tasks imported from a tracker and only when the integration was connected with write permissions; poker.sources.list shows whether it was. Only the team owner can change a game. Requires mcp:write scope.

Input parameters:

- `game_id` (string, required): The ID of the poker game.
- `task_id` (string, required): The ID of the task whose estimate goes to the tracker — see needs_sync in poker.game.tasks.list.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-qretro-retro/mcp#diagnostics

## Score history

- 2026-08-03: 80
- 2026-08-02: 79
- 2026-08-01: 38
- 2026-07-31: 38
- 2026-07-30: 24
- 2026-07-29: 24
- 2026-07-28: 24
- 2026-07-27: 24
- 2026-07-26: 21

## Links

- Remote endpoint: https://mcp.qretro.com/
- Website: https://qretro.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-qretro-retro/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-qretro-retro/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-qretro-retro/mcp