PUBLIC · READ-ONLY · FREE BETA

Reset intelligence,
inside your agent.

Ask about public Codex reset announcements, check their sources, and calculate a personal countdown from a time you provide. No model-account credentials required.

Connect a remote MCP client

Use this endpoint with a client that supports Streamable HTTP:

https://whenmodelreset.com/api/mcp

For clients using a URL-based mcpServers configuration:

{
  "mcpServers": {
    "whenmodelreset": {
      "url": "https://whenmodelreset.com/api/mcp"
    }
  }
}

Configuration formats vary by host. Add this as a remote HTTP server, not a local command. Opening the API URL in a browser is not a connection test; it accepts MCP POST requests.

Four focused tools

`get_reset_status`

Latest public signals, verification status, source links and freshness. It does not read your remaining quota.

`list_reset_events`

Paginated history, keeping global resets, banked grants, policy changes and outlooks separate.

`get_reset_updates`

Known changes since a timestamp. Consume all pages; only advance when can_advance_watermark is true. A bounded feed or failed source check cannot prove “no changes”.

`calculate_reset_window`

Timezone-aware countdown from your supplied timestamp, or explicit start and duration. No assumed platform cycle or saved personal schedule.

Try asking your agent

“What is the latest public Codex reset signal? Cite the source and tell me whether it happened or is only planned.”
“Is this announcement a global reset or a per-user banked grant?”
“My account says it recovers at 2026-10-07T17:00:00Z. Calculate the countdown in Asia/Shanghai.” Example time only, not a predicted reset.

What this beta cannot promise

Codex public intelligence is the initial supported feed. Claude and Grok public queries return “unsupported” until their evidence is ready.
A post timestamp is not necessarily the effective reset time. Date-only records stay date-only; unknown future times stay unknown.
A global announcement is not proof that your own account has recovered. Check the account’s official usage display.
This MCP does not reset quotas, access accounts, claim credits, switch subscriptions or wake your agent in the background.
Public sources can lag or fail. The response reports degraded freshness rather than claiming it is current.

Privacy and responsible use

Do not send passwords, API keys, cookies or chat transcripts. Personal calculation inputs are processed for the response and are not saved as a user profile. Hosting and client platforms may retain operational request metadata under their own policies.

No additional model is invoked for an MCP query. Public source snapshots may be cached for two minutes; read the actual source check timestamp. The beta has bounded results, body-size limits and best-effort per-instance rate protection. It is not an unlimited service or a distributed quota system.

中文接入说明

在支持远程 MCP 的 Agent 中添加上面的地址，连接方式选择 Streamable HTTP。公开只读版不需要提交模型账号或密钥。

先支持 Codex：查询公告、历史记录、时间之后的变化，以及根据你提供的时间计算个人倒计时。
公告、全局重置、个人备用卡和规则变化分别标记。来源发布时间不等于实际生效时间，也不能证明你的账号额度已经恢复。
数据源异常会明确显示降级状态；不知道下一次重置时间时返回未知，不用历史间隔编造时间表。
更新查询不是完整事件档案：数据源只保留近期快照，覆盖不足时不会允许推进检查时间，避免误认为没有更新。
它不会自动唤醒 Agent 或替你恢复任务。定时检查、提醒和执行仍由你的 Agent 或调度器负责。
个人倒计时只做本次计算，不保存为账号档案。不要上传账号凭证或完整聊天记录。

查看重置历史与来源 →

Reset intelligence,inside your agent.