com.qretro/retro

Est-ce que com.qretro/retro est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.qretro/retro » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 29 outils

• poker.game.get≈ 114 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • game_id · string · requis
    The ID of the poker game.

  Exemple d'appel

  {"name": "poker.game.get", "arguments": {"game_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• poker.game.task.reveal≈ 210 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • reveal · boolean · optionnel
    true (default) — reveal the cards and compute the estimate. false — hide them, clear the votes and the estimate.
  • game_id · string · requis
    The ID of the poker game.
  • task_id · string · requis
    The ID of the task to reveal.

  Exemple d'appel

  {"name": "poker.game.task.reveal", "arguments": {"game_id": "texte", "task_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• poker.game.task.select≈ 138 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • game_id · string · requis
    The ID of the poker game.
  • task_id · string · requis
    The ID of the task to put on the table — see poker.game.tasks.list.

  Exemple d'appel

  {"name": "poker.game.task.select", "arguments": {"game_id": "texte", "task_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• poker.game.task.sync≈ 181 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • game_id · string · requis
    The ID of the poker game.
  • task_id · string · requis
    The ID of the task whose estimate goes to the tracker — see needs_sync in poker.game.tasks.list.

  Exemple d'appel

  {"name": "poker.game.task.sync", "arguments": {"game_id": "texte", "task_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• poker.game.tasks.add≈ 147 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • tasks · array · requis
    Tasks to add: a list of objects with name and optional description.
  • game_id · string · requis
    The ID of the poker game.

  Exemple d'appel

  {"name": "poker.game.tasks.add", "arguments": {"tasks": [], "game_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• poker.game.tasks.import≈ 270 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "poker.game.tasks.import", "arguments": {"game_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• poker.game.tasks.list≈ 208 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "poker.game.tasks.list", "arguments": {"game_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• poker.games.create≈ 226 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "poker.games.create", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• poker.games.list≈ 153 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "poker.games.list", "arguments": {"limit": 1, "team_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• poker.iterations.list≈ 252 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "poker.iterations.list", "arguments": {"query": "texte", "source": "texte", "team_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• poker.sources.list≈ 158 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • team_id · string · optionnel
    Team to inspect. Required when more than one team is available — call retro.teams.list first.

  Exemple d'appel

  {"name": "poker.sources.list", "arguments": {"team_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.actions.complete≈ 89 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • action_item_id · string · requis
    The ID of the action item to mark as completed.

  Exemple d'appel

  {"name": "retro.actions.complete", "arguments": {"action_item_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.actions.create≈ 204 tokens

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

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "retro.actions.create", "arguments": {"text": "texte", "board_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.actions.list≈ 260 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "retro.actions.list", "arguments": {"limit": 1, "since": "texte", "status": "texte", "team_id": "texte", "assignee": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.actions.update≈ 194 tokens

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

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "retro.actions.update", "arguments": {"action_item_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.board.actions.list≈ 130 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • board_id · string · requis
    The ID of the board to get action items for.
  • include_completed · boolean · optionnel
    Whether to include completed action items. Default: false.

  Exemple d'appel

  {"name": "retro.board.actions.list", "arguments": {"board_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.board.health.get≈ 145 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • board_id · string · requis
    The ID of the board to get the health check report for.

  Exemple d'appel

  {"name": "retro.board.health.get", "arguments": {"board_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.board.insights.list≈ 114 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • board_id · string · requis
    The ID of the board to get insights for.

  Exemple d'appel

  {"name": "retro.board.insights.list", "arguments": {"board_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.board.messages.delete_own≈ 121 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • message_id · string · requis
    The ID of the message to delete.

  Exemple d'appel

  {"name": "retro.board.messages.delete_own", "arguments": {"message_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.board.messages.list≈ 128 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • board_id · string · requis
    The ID of the board to get messages for.

  Exemple d'appel

  {"name": "retro.board.messages.list", "arguments": {"board_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.board.messages.update≈ 110 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • text · string · requis
    New text content for the message.
  • message_id · string · requis
    The ID of the message to update.

  Exemple d'appel

  {"name": "retro.board.messages.update", "arguments": {"text": "texte", "message_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.board.roti.get≈ 114 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • board_id · string · requis
    The ID of the board to get ROTI metrics for.

  Exemple d'appel

  {"name": "retro.board.roti.get", "arguments": {"board_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.board.suggested_actions.promote≈ 231 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "retro.board.suggested_actions.promote", "arguments": {"board_id": "texte", "suggested_action_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.board.suggested_actions.reject≈ 174 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • board_id · string · requis
    The ID of the board the suggestion belongs to.
  • suggested_action_id · string · requis
    The ID of the suggested action to reject, from suggested_actions in retro.board.insights.list. Only suggestions with status "pending" can be rejected.

  Exemple d'appel

  {"name": "retro.board.suggested_actions.reject", "arguments": {"board_id": "texte", "suggested_action_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.board.summary.get≈ 119 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • board_id · string · requis
    The ID of the board to get the summary for.

  Exemple d'appel

  {"name": "retro.board.summary.get", "arguments": {"board_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.boards.list≈ 240 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "retro.boards.list", "arguments": {"since": "texte", "until": "texte", "team_id": "texte", "finished_only": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.boards.search≈ 150 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • query · string · requis
    Search query. Looks into board summaries, action items and participant cards.
  • team_id · string · optionnel
    Optional: filter search to a specific team.

  Exemple d'appel

  {"name": "retro.boards.search", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.team.members.list≈ 184 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • team_id · string · optionnel
    Team to list members for. Required when more than one team is available — call retro.teams.list first.

  Exemple d'appel

  {"name": "retro.team.members.list", "arguments": {"team_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retro.teams.list≈ 85 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "retro.teams.list", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.qretro.com