io.github.whdrnr2583-cmd/token-meter

Name: io.github.whdrnr2583-cmd/token-meter
Author: io.github.whdrnr2583-cmd

MCPcommunity

v0.1.17io.github.whdrnr2583-cmdUnknownUpdated 3mo agonpm GitHub

Local-first dashboard + MCP for Claude Code and Codex token usage. Per-MCP/tool breakdown.

One local dashboard for your Claude Code and Codex token usage. Free, MCP-aware, MIT-licensed core. npm: · GitHub: · Site: token-meter.dev Token Meter parses the JSONL files that Claude Code and Codex already write to disk and turns them into a real dashboard: cost per project, per model, per MCP tool, per hour. Your data never leaves your machine. The package is published under an npm scope ()…

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1GitHub stars

3mo agoLast update

Package

Authorio.github.whdrnr2583-cmd

LicenseUnknown

Version0.1.17

Sourcemcp-registry

npm@whdrnr2583/token-meter

GitHubwhdrnr2583-cmd/token-meter

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies60 resolved · 1 with advisories

Tool surface4 tools · none privileged

Security scan✓ Cleanv0.1.17 · 3mo agoHow well does this scan work?

MODERATE@fastify/static@8.3.0@fastify/static vulnerable to path traversal in directory listing MODERATE@fastify/static@8.3.0@fastify/static vulnerable to route guard bypass via encoded path separators

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged

Statically extracted from the published packagev0.1.17 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

usage_summaryNo description published

This tool published no description. Forge does not invent one.

recent_sessionsNo description published

This tool published no description. Forge does not invent one.

session_toolsNo description published

This tool published no description. Forge does not invent one.

refresh_dataNo description published

This tool published no description. Forge does not invent one.

0 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keywords

mcp

Alternatives

Comparing tool surfaces…

io.github.whdrnr2583-cmd/token-meter

Tools

Tools exposed

No dependency coverage