Codex Reset

io.github.suvadadepolo-blipPublished by GitHub account suvadadepolo-blipv1.0.0Updated Nov 2, 2026

Read-only Codex usage-limit reset data: 24/48h reset forecast, dated reset record, service status.

The publisher's own server: RemoveDuplicates.org

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Read-only MCP server that gives an assistant Codex usage-limit reset forecasts, a dated reset history and current Codex service status.

What you can do
  • Check the probability of a Codex usage-limit reset in the next 24 and 48 hours, with confidence, the last confirmed reset and any active official signal
  • Browse a dated, newest-first record of verified resets and banked reset grants, filtered by group, date range and result limit, each with its source link
  • Look up the current Codex service state to tell an outage apart from a usage limit
  • Request responses in English, Chinese, Japanese or Spanish for the human-readable copy
When to use it
Useful when you work with OpenAI Codex and want to know whether waiting for a usage-limit reset is worthwhile, when the last verified reset happened and where it was announced, or whether errors come from an outage rather than a limit.
Requirements
A remote Streamable HTTP endpoint; nothing to install or run locally. No API key, sign-up or session is needed. Clients that only speak stdio can bridge to it with a local npx helper. Network access to the endpoint is required.
Before you install
All three tools are read-only and the server keeps no session or account. The forecast is explicitly a probability, not a promise, so treat it as an estimate. Reuse of the data in a site, app, bot message, dashboard or API requires naming and linking the source; personal use needs no visible credit. It is an independent community project, not affiliated with OpenAI.

Installation

In SourceWeft

  1. Open Codex Reset in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.suvadadepolo-blip%2Fcodex-reset/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "codex-reset": {
      "type": "http",
      "url": "https://codex-reset.com/mcp"
    }
  }
}

README

Codex Reset MCP server

[smithery badge]

Read-only facts about OpenAI Codex usage-limit resets, served by codex-reset.com over the Model Context Protocol.

This repository holds the client configuration and directory metadata for the hosted server. There is nothing to install or run: the server lives at the endpoint above, and its source is not published here.

Tools

All three tools are read-only (readOnlyHint: true) and read the same data as the site's public JSON API, so an agent and a browser never disagree.

ToolReturnsArguments
get_reset_forecastProbability of a Codex usage-limit reset in the next 24 and 48 hours, confidence, the last confirmed reset and any active official signal. A forecast, not a promise.locale
get_reset_timelineDated record of verified resets and related announcements, newest first, each with its source URL.group (reset | boost | unlock | credits), from, to (YYYY-MM-DD), limit (1–50, default 10), locale
get_codex_statusCurrent Codex service state, to tell an outage apart from a usage limit.locale

locale is en, zh, ja or es and changes only the human-readable copy.

Example prompts

  • "Is Codex likely to reset its usage limits in the next 24 hours?"
  • "When was the last verified Codex usage-limit reset, and where was it announced?"
  • "List every Codex reset from August 2026 with its source link."
  • "I'm getting errors in Codex. Is that an outage or did I hit my usage limit?"
  • "Should I wait for a reset or keep working? Check the forecast and the service status."

Setup

Claude Code

sh
claude mcp add --transport http codex-reset https://codex-reset.com/mcp

Or in .mcp.json:

json
{  "mcpServers": {    "codex-reset": { "type": "http", "url": "https://codex-reset.com/mcp" }  }}

This repository is also a Claude Code plugin (.claude-plugin/plugin.json + .mcp.json).

Codex CLI / IDE extension

~/.codex/config.toml:

toml
[mcp_servers.codex-reset]url = "https://codex-reset.com/mcp"

This repository is also a Codex plugin (.codex-plugin/plugin.json: the MCP server plus a codex-reset skill), listed in awesome-codex-plugins and the HOL plugin registry. The two config.toml lines above are all a plain Codex setup needs.

Cursor

.cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

json
{  "mcpServers": {    "codex-reset": { "url": "https://codex-reset.com/mcp" }  }}

VS Code (GitHub Copilot)

.vscode/mcp.json:

json
{  "servers": {    "codex-reset": { "type": "http", "url": "https://codex-reset.com/mcp" }  }}

Gemini CLI

sh
gemini extensions install https://github.com/suvadadepolo-blip/codex-reset-mcp

Clients that only speak stdio

sh
npx -y mcp-remote https://codex-reset.com/mcp

Check it by hand

sh
curl -sS https://codex-reset.com/mcp \  -H 'content-type: application/json' \  -H 'accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Where it is listed

Terms

Reuse is free and keyless on one condition: credit. A site, app, bot message, dashboard, MCP tool or API that passes this data on names the source and links to it on the same surface: "Data: codex-reset.com", linked to https://codex-reset.com/. Personal use needs no visible credit. Full wording: codex-reset.com/developers and the terms of use.

Independent community project, not affiliated with OpenAI. "Codex" and "ChatGPT" are trademarks of OpenAI and are used only to describe what is being tracked.

License

The configuration files in this repository are MIT-licensed. The data served by the endpoint is covered by the terms above.

Source: README.md at commit 5a4a716

Tools

3

get_reset_forecast

Codex reset forecast

Current probability that OpenAI resets Codex usage limits in the next 24 and 48 hours, with confidence, the last confirmed reset time and any active official signal. A forecast, not a promise.

Parameterslocale

get_reset_timeline

Codex reset record

Codex reset history: dated record of verified Codex usage-limit resets and banked reset grants (group credits), newest first, each with its source URL.

Parameterstofromgrouplimitlocale

get_codex_status

Codex service status

Current OpenAI Codex service state as tracked by codex-reset.com, to tell an outage apart from a usage limit.

Parameterslocale

Version history

1
  1. v1.0.0LatestSep 24, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Removeduplicates integrations