Skip to content

Codex Reset Monitor MCP server

io.github.evanyuki/codex-reset-monitorevanyukistreamable-httpv1.0.0Scanned

Verified Codex global reset history, banked-reset sightings and cadence statistics by Agenai.

3 tools: 3 only read.

Tools: 0 delete, 0 irreversible, 0 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • 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.
Govern this server →

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 Monitor MCP server can do

The Codex Reset Monitor MCP server is published by the GitHub account evanyuki. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.0.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.

3 tools

Only reads 3Show 3 read-only tools
  • get_latest_resetThe most recent verified Codex global reset and the most recent banked-reset sighting, with totals and data coverage.No findings

    Why it is in this group

    • The name "get_latest_reset" says "get": a word for reading.
    Description, as the server wrote it
    The most recent verified Codex global reset and the most recent banked-reset sighting, with totals and data coverage. History from public monitoring signals maintained by Agenai.

    Annotations the server declares

    • title: Latest Codex reset
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_reset_statsCadence statistics over the full recorded history: total verified resets, resets in the last 30/90 days, gap between resets (average/median/min/max days), monthly counts and announ…No findings

    Why it is in this group

    • The name "get_reset_stats" says "get": a word for reading.
    Description, as the server wrote it
    Cadence statistics over the full recorded history: total verified resets, resets in the last 30/90 days, gap between resets (average/median/min/max days), monthly counts and announcement-time distribution (Asia/Shanghai). History only — not a prediction.

    Annotations the server declares

    • title: Codex reset cadence statistics
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_reset_eventsList recorded Codex events, newest first.No findings

    Why it is in this group

    • The name "list_reset_events" says "list": a word for reading.
    Description, as the server wrote it
    List recorded Codex events, newest first. type 'reset' = verified global resets, 'credits' = banked-reset sightings, 'all' = both.

    Annotations the server declares

    • title: List Codex reset events
    • 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 private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:23 UTC, unchanged since Nov 5, 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.

  1. Tools3 changed.~3 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http codex-reset-monitor https://www.agenai.cc/mcp
claude mcp add --transport http codex-reset-monitor https://www.agenai.cc/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__codex-reset-monitor__get_latest_reset",
      "mcp__codex-reset-monitor__list_reset_events",
      "mcp__codex-reset-monitor__get_reset_stats"
    ],
    "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-reset-monitor. Review it before you use it.

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/io.github.evanyuki/codex-reset-monitor/verify?hash=3e8d943a5ccd9e653a1b3a7ce63fc61b40f4877aef8146b1c9842a8f492ea57d" | jq -e '.changed == false'

Pinned hash 3e8d943a5ccd, from Nov 17, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.evanyuki/codex-reset-monitor/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.evanyuki/codex-reset-monitor
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.evanyuki/codex-reset-monitor.svg)](https://radar.anlyon.com/servers/io.github.evanyuki/codex-reset-monitor)

Source: MCP Registry. Synced Nov 4, 2026, 07:17 UTC.

Codex Reset Monitor MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Codex Reset Monitor MCP server safe?

No scan can promise that. What its definitions show: 3 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 Monitor 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 Monitor 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 Monitor MCP server have?

3 tools: 3 read. get_latest_reset, list_reset_events and get_reset_stats.

Does the Codex Reset Monitor MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Codex Reset Monitor 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 Monitor MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.