Is the Qretro Retro MCP server down?

mcp-registry/com.qretro/retro · v1.3.0

healthy
Last checked 2026-10-27 01:57 UTC · handshake 869ms

As of 2026-10-27 01:57 UTC, the Qretro Retro MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 40 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
99.3%
checks observed
1,735
outages (90d)
40
tools
29

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

Point your MCP client at this streamable-http endpoint: https://mcp.qretro.com

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 2 warning(s) across 29 tool(s); ~4,714 tokens of tool definitions.
Scores higher than 14% of 15,771 MCP servers Glimind has audited.
Its tool list costs an agent ~4,714 tokens per session — more than 60% of servers.
74 → 78 since 2026-10-21
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints35
Token cost100
Client compatibility20
Protocol100
Reliability100
Stability100

What to fix (4)

29 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).

Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →

Tools: poker.game.get, poker.game.task.reveal, poker.game.task.select, poker.game.task.sync, poker.game.tasks.add and 24 more

5 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: poker.games.create, retro.actions.create, retro.actions.update, retro.board.messages.delete_own, retro.board.messages.update

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

13 of 29 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: poker.game.task.reveal, poker.game.task.select, poker.game.task.sync, poker.game.tasks.add, poker.game.tasks.import and 8 more

Auto-fix: 29 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.qretro%2Fretro/fixes

poker.game.get 1 change
{
  "name": "poker_game_get",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "game_id"
    ],
    "properties": {
      "game_id": {
        "type": "string",
        "description": "The ID of the poker game."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get Poker Game Tool"
}
poker.game.task.reveal 1 change
{
  "name": "poker_game_task_reveal",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "game_id",
      "task_id"
    ],
    "properties": {
      "reveal": {
        "type": "boolean",
        "description": "true (default) — reveal the cards and compute the estimate. false — hide them, clear the votes and the estimate."
      },
      "game_id": {
        "type": "string",
        "description": "The ID of the poker game."
      },
      "task_id": {
        "type": "string",
        "description": "The ID of the task to reveal."
      }
    }
  },
  "annotations": {},
  "title": "Reveal Poker Task Tool"
}
poker.game.task.select 1 change
{
  "name": "poker_game_task_select",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "game_id",
      "task_id"
    ],
    "properties": {
      "game_id": {
        "type": "string",
        "description": "The ID of the poker game."
      },
      "task_id": {
        "type": "string",
        "description": "The ID of the task to put on the table — see poker.game.tasks.list."
      }
    }
  },
  "annotations": {},
  "title": "Select Poker Task Tool"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.qretro/retro"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.qretro/retro"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.qretro%2Fretro.svg)](https://glimind.com/server/mcp-registry%2Fcom.qretro%2Fretro?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.qretro%2Fretro?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.qretro%2Fretro.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.qretro%2Fretro.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.qretro%2Fretro?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7d0ba54e0eabbda3…, first seen 2026-10-17, included at leaf 10209 of 76,725. Version history · verify what your client received.

Tools (29)

Compare: most reliable knowledge servers · most reliable productivity servers · most reliable data servers · most reliable retrieval servers · most reliable analytics servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Qretro Retro MCP server down right now?

As of 2026-10-27 01:57 UTC, the Qretro Retro MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 40 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Qretro Retro MCP server provide?

Qretro Retro MCP server advertises 29 tools, including poker.game.get, poker.game.task.reveal, poker.game.task.select, poker.game.task.sync, poker.game.tasks.add.

How do I install Qretro Retro MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.qretro.com

Is the Qretro Retro MCP server safe to connect to an AI agent?

Glimind scanned all 29 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Qretro Retro MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve