Developers

Codex reset API and MCP for your tools

The Codex reset API and MCP server behind this site belong to codex-reset.com: free, keyless, and open to any agent or script that credits the source.

MCP: /mcp
REST: /api
Auth: none

MCP

Streamable HTTP · no key

codex-reset.com runs a read-only MCP server. Its tools answer from the same data as the JSON endpoints: the live forecast, the dated reset record and Codex service status. Show "Data: codex-reset.com" wherever an answer appears.

Streamable HTTP

https://codex-reset.com/mcp

Tools an agent can call

Tool	What it returns
`get_reset_forecast`	Chance of a reset in the next 24 and 48 hours, the last confirmed reset and any live promise.
`get_reset_timeline`	Verified resets and related announcements, newest first, each with its source post.
`get_codex_status`	Current Codex service state, to tell an outage from a usage limit.

Add it to your agent

One line of setup, then ask whether Codex reset

Claude Code

HTTP transport, for one project or for your user.

CLI

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

.mcp.json

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

Codex

The Codex CLI and the IDE extension both read ~/.codex/config.toml.

~/.codex/config.toml

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

Cursor

Per project in .cursor/mcp.json, or for every project in ~/.cursor/mcp.json.

.cursor/mcp.json

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

~/.cursor/mcp.json

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

Any other client

Clients that speak Streamable HTTP take the bare URL. To check the server by hand:

curl

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"}'

REST

JSON · CORS open · no key

The same data the MCP tools return. Send a User-Agent that names your project and how to reach you, poll at most once a minute, and show "Data: codex-reset.com" where the data appears.

API catalog llms.txt Full reference

Method	Path	What it returns
`GET`	/api/forecast	Reset odds for 24 and 48 hours, the last reset time and any live promise.
`GET`	/api/timeline	Every recorded reset, banked grant and boost with its UTC time and source post.
`GET`	/api/feed	Tibo's recent reset-related posts as ingested, with their age.
`GET`	/api/status-history	Codex service state and recent OpenAI incidents.
`GET`	/api/juice	Observed Codex model and reasoning-effort readings.

curl

curl -sS -H 'User-Agent: yourproject/1.0 (+https://yourproject.example)' https://codex-reset.com/api/forecast

JavaScript

const res = await fetch('https://codex-reset.com/api/forecast');
const f = await res.json();
console.log(f.probabilities.rounded_24h, f.last_reset_at); // Data: codex-reset.com

Browser alerts

On this device, with the site closed

Allow notifications once. When a reset is confirmed, the site sends a Web Push message through your browser's push service, so it arrives even with every tab of this site closed.

Alerts

Press Browser alert and allow notifications when the browser asks.
Close the tab if you like; nothing has to stay open.
A notification appears when Tibo confirms a reset. Press the button again to stop.

Email alerts are on the alerts page, and the MCP server is for agents. On an iPhone or iPad, add the site to your Home Screen first.