MCP.Market

Codex Reset Tracker MCP server

online · 100% uptime
by tokenusage.dev·dev.tokenusage/codex·v1.1.0

Codex reset tracker: usage-limit reset announcements from @thsottiaux on X. Read-only, no key.

B75/100grade B
What users say
No reviews yet
Be the first
Safety scan
B75/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Codex Reset Tracker yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Codex Reset Tracker tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Codex Reset Tracker compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
146 ms
faster than 74% of 30,031 servers

Release history: 2 versions in the registry since 2026-10-09, latest 2026-10-21, typically one every 12 days.

Install Codex Reset Tracker in Claude Code, Cursor or VS Code

claude mcp add --transport http codex https://tokenusage.dev/mcp
Add to Cursor

Codex Reset Tracker: common questions

Is Codex Reset Tracker MCP server safe?
Mostly: it is graded B (75/100). Read the Codex Reset Tracker safety report
How do I install Codex Reset Tracker?
It runs remotely at tokenusage.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Codex Reset Tracker need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Codex Reset Tracker maintained?
The latest release is v1.1.0.
Is Codex Reset Tracker up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Codex Reset Tracker compare with other MCP servers?
safety score 75/100 (higher than 45% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 146 ms (faster than 74% of 30,031 servers). Full comparison.