Skip to content
Review Times logo

Review Times MCP server

Which MCP servers are Review Times's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Review Times

Whose server it is
  • Registry namefyi.reviewtimes/review-timesverified in the MCP registry

The registry name sits under reviewtimes.fyi. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools2
  • Server calls itselfreviewtimes
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 51 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check current review wait times for each store; report your own submission to track its wait.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "check current review wait times for each store", the likely first call is review_times.
  • For "report your own submission to track its wait", the likely first call is report_submission.
  • Parameters are untyped or undescribed in 1 of 2 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer158 ms
  • Space in an agent's context≈ 388 tokensthe definitions of all its tools (2), which an agent carries on every turn
  • Tool definitionsA · 92 of 100
  • Typed results2 of 2 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 2

What an agent can do with it

  • can do · check current review wait times for each store
  • not sure · compare approval and rejection timing before submitting
  • can do · report your own submission to track its wait

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-26
  • review_times

    How long AI app, connector and plugin stores take to review submissions. Omit store for all stores. Returns typical wait (median days to decision), counts, pace and how review works.

  • report_submission

    Add the user's own submission to a store so others can see real wait times. Only call with the user's permission and for a real submission. The private link to update the report later is emailed to the address given, never returned in the…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "review-times": {
      "type": "http",
      "url": "https://reviewtimes.fyi/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http reviewtimes https://reviewtimes.fyi/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://reviewtimes.fyi/mcp as a custom connector in the settings.

OpenAPI spec

7 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.