Codex Reset Tracker MCP server
dev.tokenusage/codextokenusage.devstreamable-httpv1.1.0Scanned
Codex reset tracker: usage-limit reset announcements from @thsottiaux on X. Read-only, no key.
2 tools: 2 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Codex Reset Tracker MCP server can do
The Codex Reset Tracker MCP server is published by tokenusage.dev, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (get_codex_reset_calendar); 2 tools bring in text other people can write (get_codex_reset_announcements and get_codex_reset_calendar).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Only reads 2Show 2 read-only tools
get_codex_reset_announcementsCodex usage-limit reset announcements recorded by tokenusage.dev's Reset Alerts from @thsottiaux's public posts on X, newest first (at most 50): each post's link, when it was poste…Reads text others writeNo findings
Why it is in this group
- The name "get_codex_reset_announcements" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
Description, as the server wrote it Codex usage-limit reset announcements recorded by tokenusage.dev's Reset Alerts from @thsottiaux's public posts on X, newest first (at most 50): each post's link, when it was posted, when this site recorded it and resetType, plus when the monitor last checked X successfully. resetType is automatic, banked or both; null means recorded before Reset Alerts recorded reset types. A banked reset grant saves a reset for eligible users to apply later and does not itself refill limits. An announcement may describe a forthcoming event or one already completed; a post is not proof that any account's limit was reset. Open its url for the exact wording and eligibility. Only @thsottiaux is watched. Unofficial, not affiliated with OpenAI. Source: https://tokenusage.dev/resets
Annotations the server declares
- title: Codex reset announcements
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_codex_reset_calendarCodex usage-limit reset announcements recorded by tokenusage.dev's Reset Alerts from @thsottiaux's public posts on X, grouped by UTC calendar date, newest dates first, with posts w…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_codex_reset_calendar" says "get": a word for reading.
What it can reach
- private-dataThe name "get_codex_reset_calendar" says "get" and "calendar": it reads calendars.
- private-dataThe description's first sentence says "calendar": it reads calendars.
- untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
Description, as the server wrote it Codex usage-limit reset announcements recorded by tokenusage.dev's Reset Alerts from @thsottiaux's public posts on X, grouped by UTC calendar date, newest dates first, with posts within each date newest first (at most 50 announcements in total). Optional month selects a UTC month written YYYY-MM. Dates are UTC; only dates with recorded announcements are returned. Only announcements this monitor recorded from @thsottiaux are shown, at most the 50 newest; this is not a complete history. A date without an entry does not mean no reset was announced. Each item has postId, url, postedAt and resetType. resetType is automatic, banked or both; null means recorded before Reset Alerts recorded reset types. A banked reset grant saves a reset for eligible users to apply later and does not itself refill limits. An announcement may describe a forthcoming event or one already completed; a post is not proof that any account's limit was reset. Open its url for the exact wording and eligibility. Unofficial, not affiliated with OpenAI. Source: https://tokenusage.dev/resets
Annotations the server declares
- title: Codex reset calendar
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http codex https://tokenusage.dev/mcpclaude mcp add --transport http codex https://tokenusage.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__codex__get_codex_reset_announcements",
"mcp__codex__get_codex_reset_calendar"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as codex. Review it before you use it.
Capability tags behind 2 rules
- mcp__codex__get_codex_reset_announcements untrusted-input
- mcp__codex__get_codex_reset_calendar private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.tokenusage/codex/verify?hash=e226560af99fe71a1c0ac156b226f33f96f77728eebff21d9fa4a414c31673a6" | jq -e '.changed == false'Pinned hash e226560af99f, from Nov 8, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.tokenusage/codex/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.tokenusage/codex)Source: MCP Registry · repository. Synced Oct 21, 2026, 23:17 UTC.
Codex Reset Tracker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Codex Reset Tracker MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Codex Reset Tracker MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Codex Reset Tracker MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Codex Reset Tracker MCP server have?
- 2 tools: 2 read. get_codex_reset_announcements and get_codex_reset_calendar.
Does the Codex Reset Tracker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Codex Reset Tracker MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Codex Reset Tracker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.