Connect with MCP

Query public reset and schedule records directly from Codex, Claude Code or Cursor

No API key20 requests / hourUTC · milliseconds

Let AI install it

Copy this prompt into Codex, Claude Code or Cursor and let your AI client handle installation and verification

Set up the Did Codex Reset MCP server in my current AI client so I can query public Codex reset and schedule records, and verify the setup after installation.

Server name: didcodexreset
Endpoint: https://did-codex-reset.com/mcp
Transport: Streamable HTTP, anonymous access, no API key required.

Identify the current client (Codex, Claude Code or Cursor) and inspect its existing MCP settings. Add or update this server at user scope using the client's supported CLI or configuration format, preserving other servers and settings. If this environment cannot identify the client or modify local configuration, explain what is missing and give the exact steps for my client.

Verify the configuration and connection, and check that get_latest_reset_record and list_reset_records are discoverable. Report the configuration location, verification result and any remaining enable, reload or new-session steps. If verification fails, report the actual error without claiming installation succeeded.

Clients

Streamable HTTP

MCP URLhttps://did-codex-reset.com/mcp

Choose your client and copy its configuration, then enable Did Codex Reset in the client’s MCP settings

codex mcp add didcodexreset --url https://did-codex-reset.com/mcp

claude mcp add --transport http --scope user didcodexreset https://did-codex-reset.com/mcp

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

Codex: configure with config.toml

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

Tools

Read only · no credentials

`get_latest_reset_record`

Newest matching record, or null. Same payload as GET /records/latest.

`list_reset_records`

Paged list, max 10 items. Same payload as GET /records.

Parameter	Default	Meaning
`kind`	`all`	all (default), reset_scheduled, or reset_completed. all is the live public signal list and omits fulfilled schedules. Scheduled filter includes fulfilled and elapsed history; undone or dismissed records are omitted.
`page`	`1`	1-based page index. Pages past the end return an empty items array and keep the requested page.
`pageSize`	`10`	1–10, default 10.

Both tools accept kind; page and pageSize apply only to the list tool; use JSON integers for pagination, extra keys and wrong types are rejected

Response fields and record semantics

Limits & errors

20 requests / hour

Up to 20 requests in any rolling 3600 seconds, shared by Open API data endpoints and MCP query tools.

Requests admitted to either data endpoint or an MCP query tool count once, even if validation or processing later fails. Handshake, tool listing, rejected protocol requests, documentation, the specification, skill downloads and OPTIONS do not count. A shared outbound IP shares quota. Admitted responses, including successful 200s, include X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Window and X-RateLimit-Reset. Those headers are omitted only when limiting is disabled. Retry-After is sent only with HTTP 429.

Tool errors return isError and a structured error code; rate_limited includes retryAfter; unknown tools and malformed requests return MCP protocol errors, whose HTTP status depends on the protocol version