Skip to content
MCPSTAMP
MCP server report

Retro MCP server

com.qretro/retro

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 85 of 100 (grade B), higher than 31.2% of the 33,003 registry servers that responded over HTTPS that day. Ready for Gemini and MCP Registry. Not ready for Claude and ChatGPT.

Measured facts

Score
85B
Sign-in
OAuth
Tools listed
29
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by readOnlyHint or destructiveHint on every tool.
ChatGPT app directory Not ready Blocked by issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), readOnlyHint or destructiveHint on every tool and Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT).
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

5 checks to fix

  1. Fails

    readOnlyHint or destructiveHint on every tool

    tool_annotations

    Blocks Claude and ChatGPT.

    Measured 13/29 tools set neither readOnlyHint nor destructiveHint: retro.board.messages.update, retro.board.messages.delete_own, retro.actions.create, retro.actions.upda

    Set annotations.readOnlyHint: true on read-only tools and destructiveHint: true on tools that modify or delete data (Claude needs one of them on every tool; ChatGPT needs all three hints, see tool_open_world).

  2. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 29/29 tools miss an explicit hint: retro.teams.list, retro.team.members.list, retro.boards.list, retro.actions.list, retro.board.messages.list and 24 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  3. Fails

    issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT)

    auth_chatgpt_metadata

    Blocks ChatGPT.

    Measured token_endpoint_auth_methods_supported missing

    Use the exact metadata "issuer" string in the protected resource metadata authorization_servers list (no trailing-slash or case differences), and list token_endpoint_auth_methods_supported (for example ["none"] for public clients) in the au

  4. Warning

    Tool names are valid and portable

    tool_names

    Measured Not portable (dots, over 64 chars or leading digit/dash): retro.teams.list, retro.team.members.list, retro.boards.list, retro.actions.list, retro.board.messages

    Rename tools to ^[A-Za-z_][A-Za-z0-9_-]{0,63}$ so every client and model API accepts them.

  5. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured HTTP 401 instead of a JSON-RPC error

    Route the method first and answer unknown methods with JSON-RPC error -32601 before the auth check, or return a JSON-RPC error body with the 401.

22 checks passed

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, GET answers SSE or 405, initialize latency, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised, tools/list returns tools, inputSchema is an object schema, Human-readable title on every tool, Tool descriptions.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Retro

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.qretro.com%2F)](https://www.mcpstamp.com/r/com-qretro-retro/)

HTML

<a href="https://www.mcpstamp.com/r/com-qretro-retro/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.qretro.com%2F" alt="McpStamp score" height="20"></a>
Registry entry

About this server

QRetro retrospectives and planning poker over MCP: boards, action items, poker games, estimates.
Registry name
com.qretro/retro
Remote URL
https://mcp.qretro.com/
Version
1.3.0
Website
qretro.com
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade B servers

All grade B servers · All server reports · State of MCP readiness, November 2026