codexwatch
PYPI · CODEXWATCH-CLI
OpenAI Codex usage from your local logs: tokens, API-equivalent cost and plan limits.
Available components
Last scanned (3 hours ago)
Scores higher than 78% of PyPI servers
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to psychofict/codexwatch). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 367 tokens (~61/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Package version: 1.0.1 → 1.0.2 functional
- 4 Nov 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed pypi/codexwatch-cli@1.0.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | psychofict/codexwatch |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/psychofict/codexwatch/.github/workflows/release.yml@refs/tags/v1.0.2 |
| Rekor log index | 3692359295 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:768422574ed8a88886567ec91320afa48ee6557f6bae7320731017329767e52c |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
budget_status ~41
The user's codexwatch budgets (dollar, token or plan-window caps) with how much of each is used and whether it is near or over its limit.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
daily ~32
Tokens and API-equivalent dollars per local day, oldest first, with empty days included.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
plan_limits ~70
Where the ChatGPT plan's Codex limits stand now: each window's percent used, reset time, burn rate per hour and projected time it fills, read from the newest session log. With codexhop installed, also every saved account's last reading and the account with the most 5-hour room.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quota_forensics ~77
What each percentage point of the plan cost in API-equivalent dollars and tokens, per window and per day, plus rises in a window that the local logs cannot explain (usage from another machine, ChatGPT itself or cloud tasks, or a metering change).
| Name | Type | Req | Description |
|---|---|---|---|
| window | string | – | only windows of this length; both when omitted |
No output schema declared.
No examples provided.
sessions ~34
The most recent Codex sessions with title, project, models, turns, tokens and dollar value.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
usage_summary ~82
Codex token usage and its API-equivalent dollar value for a period: totals, cache hit rate, and the top models and projects. Dollar figures are estimates at OpenAI API prices; tokens of models with no published price are counted separately.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | today, the last 7 or 30 days, this calendar month, or all history |
No output schema declared.
No examples provided.
How do I install the codexwatch MCP server?
codexwatch runs locally as a PyPI package, launched with uvx codexwatch-cli mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · codexwatch-cli
claude mcp add psychofict-codexwatch -- uvx codexwatch-cli mcp
What is the codexwatch MCP server?
codexwatch is an MCP server listed in the public MCP registry as io.github.psychofict/codexwatch. OpenAI Codex usage from your local logs: tokens, API-equivalent cost and plan limits. This page covers its PyPI package (codexwatch-cli).
Is the codexwatch MCP server safe to use?
codexwatch scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the codexwatch MCP server expose?
codexwatch exposes 6 tools: usage_summary, plan_limits, quota_forensics, sessions, daily, budget_status. Their descriptions and schemas cost roughly 336 tokens of context every time the server is loaded.
Is the codexwatch MCP server still maintained?
codexwatch is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the codexwatch MCP server under?
codexwatch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the codexwatch MCP server?
VerifyMCP ran 16 checks on codexwatch, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.