# TokenBar (mcpb · TokenBar.mcpb)

AI usage limits (Claude Code, Codex, Copilot, Windsurf): check budget and time until reset.

- Trust score: 43/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- mcpb · `TokenBar.mcpb`: 43/100 (this document), [markdown](https://verifymcp.io/servers/chaconlucas-tokenbar/tokenbar.md), [page](https://verifymcp.io/servers/chaconlucas-tokenbar/tokenbar)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/ChaconLucas/tokenbar/releases/download/v0.5.3/TokenBar.mcpb`
- Transport: `stdio`
- SHA-256: `3832d2a22db011858c8492aa3ab3083952abaf0d80e64887d7c4daa670a28c57`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 426 tokens (~142/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the TokenBar MCP server?

TokenBar ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 3832d2a22db011858c8492aa3ab3083952abaf0d80e64887d7c4daa670a28c57; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/ChaconLucas/tokenbar/releases/download/v0.5.3/TokenBar.mcpb`
- SHA-256: `3832d2a22db011858c8492aa3ab3083952abaf0d80e64887d7c4daa670a28c57`

### Verify on macOS / Linux

```bash
echo "3832d2a22db011858c8492aa3ab3083952abaf0d80e64887d7c4daa670a28c57  TokenBar.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\TokenBar.mcpb).Hash -eq "3832d2a22db011858c8492aa3ab3083952abaf0d80e64887d7c4daa670a28c57"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 41, +1)

- [functional improvement] Security disclosure: fail → pass

### 2026-10-18 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 39)

First indexed and scored.

## MCP tools (3)

### `get_usage` (~114 tokens)

Get AI usage limits

Current usage of AI subscription limits (Claude Code, Codex, GitHub Copilot, Windsurf and any AI the user added to TokenBar). For each AI: windows (usually 5h and 7d) with usedNow (% used right now, 0 after the reset time), resetsAt (unix s) and resetsInSeconds.

Input parameters:

- `provider` (string): Optional provider id: "claude", "codex", "copilot", "windsurf" or another id. Omit for all.

### `time_until_reset` (~99 tokens)

Time until a usage limit resets

Seconds (and human text) until a provider's usage window resets. Default window: the first (5h).

Input parameters:

- `provider` (string, required): Provider id, e.g. "claude" or "codex".
- `window` (string): Limit window: "5h" (short window, the first) or "7d" (long window, the second). Labels like "1d" or "30d" also work.

### `check_budget` (~156 tokens)

Check whether there is usage budget left

Checks if a provider is below a usage threshold, so you can decide whether to start a long or expensive task now or postpone it until the limit resets. Without `window`, checks every window and reports the tightest one. Returns ok, usedNow, resetsInSeconds and advice.

Input parameters:

- `max_percent` (number): Budget threshold in percent (default 80). ok = usedNow < max_percent.
- `provider` (string, required): Provider id, e.g. "claude" or "codex".
- `window` (string): Limit window: "5h" (short window, the first) or "7d" (long window, the second). Labels like "1d" or "30d" also work.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/chaconlucas-tokenbar/tokenbar#diagnostics

## Score history

- 2026-10-23: 43
- 2026-10-22: 42
- 2026-10-21: 42
- 2026-10-20: 41
- 2026-10-19: 40
- 2026-10-18: 40
- 2026-10-17: 39
- 2026-10-16: 39

## Common questions

### What is the TokenBar MCP server?

TokenBar is an MCP server listed in the public MCP registry as io.github.ChaconLucas/tokenbar. AI usage limits (Claude Code, Codex, Copilot, Windsurf): check budget and time until reset. This page covers its MCPB bundle (https://github.com/ChaconLucas/tokenbar/releases/download/v0.5.3/TokenBar.mcpb).

### Is the TokenBar MCP server safe to use?

TokenBar scores 43 out of 100 on VerifyMCP. 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 TokenBar MCP server expose?

TokenBar exposes 3 tools: get_usage, time_until_reset, check_budget. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.

### What licence is the TokenBar MCP server under?

TokenBar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/ChaconLucas/tokenbar
- Website: https://chaconlucas.github.io/tokenbar/
- Changelog RSS feed: https://verifymcp.io/servers/chaconlucas-tokenbar/tokenbar.xml
- Changelog JSON feed: https://verifymcp.io/servers/chaconlucas-tokenbar/tokenbar.json
- HTML version of this page: https://verifymcp.io/servers/chaconlucas-tokenbar/tokenbar