Remote MCP · Endpoint

Codex Reset Tracker MCP server

No. Codex Reset Tracker answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://tokenusage.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.tokenusage/codex
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
101 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Codex reset tracker: usage-limit reset announcements from @thsottiaux on X. Read-only, no key.
Listing
From the official MCP registry (active).
Recent checks of Codex Reset Tracker
CheckedResultHandshake
2 hours agoHandshake completed101 ms
1 day agoHandshake completed116 ms
2 days agoHandshake completed198 ms
2 days agoHandshake completed170 ms
4 days agoHandshake completed109 ms
7 days agoHandshake completed114 ms
9 days agoHandshake completed116 ms
12 days agoHandshake completed128 ms
14 days agoHandshake completed124 ms
16 days agoHandshake completed164 ms
18 days agoHandshake completed114 ms
20 days agoHandshake completed100 ms
22 days agoHandshake completed120 ms
24 days agoHandshake completed138 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Codex Reset Tracker and makes no claim about it beyond what these checks measured.