Claude Cup — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Claude session-event measurement and terminal competition tools: What session information is sent to the worldwide leaderboard, and can local MCP tracking remain separate?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Tracking Claude Code usage and local developer productivity metrics.

What we know

Claude Cup provides terminal/browser dashboards for Claude Code activity, usage metrics and a local MCP/hooks integration.

Maintenance / activity evidence

claude-cup 0.9.12 published 2026-07-19T14:29:05.169Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Reads local Claude Code activity/transcript data and changes local integration settings. Writes: Register hooks; Change local eco-mode settings.
No service authentication documented for the local dashboard.
Sensitive access: Claude Code transcripts, Developer credential-pattern metadata

The integration handles local developer transcripts and credential-pattern metadata; review its local storage and dashboard exposure.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

What session information is sent to the worldwide leaderboard, and can local MCP tracking remain separate?

The bounded review of the publisher's documented Claude session-event measurement and terminal competition tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

The integration handles local developer transcripts and credential-pattern metadata; review its local storage and dashboard exposure.
Reads local Claude Code activity/transcript data and changes local integration settings.
No service authentication documented for the local dashboard.
The package states data stays in its local directory; credential-pattern checks operate on local metadata.
Reviewed write actions: Register hooks; Change local eco-mode settings
Sensitive access: Claude Code transcripts, Developer credential-pattern metadata
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Verified repository identity
Reliable 30-day download metric
It is a community package, not an Anthropic product.
The reviewed package documents local transcript and credential-pattern analysis, which is privacy-sensitive.

Original activity observations

claude-cup 0.9.12 published 2026-07-19T14:29:05.169Z

Technical identity

npm/claude-cup

Exact implementation source: https://www.npmjs.com/package/claude-cup ↗
Reviewed resource type: MCP Server
Package identity: npm:claude-cup
Service endpoint: http://localhost:4690

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

Package registry ↗
claude-cup
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
TUI/web dashboard tool, publisher does not document this command as MCP stdio server; do not register as one
Targeted 2026-10-13 re-research: Standalone TUI/web UI, not MCP server: npx claude-cup starts UI, not MCP tool transport.
Standalone TUI/web UI, not MCP server: npx claude-cup starts UI, not MCP tool transport.
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Claude Cup provides TUI/web app, not documented as MCP protocol stdio server.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / launch TUI application
Publisher instructions
TUI/web dashboard tool, publisher does not document this command as MCP stdio server; do not register as one | Publisher npm README revisited on 2026-10-14; exact identity retained. The README emphasizes TUI and hook integration; independent MCP transport not verified.
Reviewed setup example · Publisher instructions
npx claude-cup
Configure / authenticate
MCP100 setup guide
Claude Cup primarily TUI and Claude Code hooks; published README does not establish a portable standalone MCP command. Do not invent client registration.
Check connection
Suggested check
Confirm TUI starts or publisher hook integration shows local metrics; no generic MCP tool verification.
Remove / uninstall / revoke
MCP100 setup guide
Publisher explicitly offers npm global uninstall for Claude Cup. Stop/disable optional Claude Code hook integration separately. `~/.claude-jar/` is local data and must not be deleted automatically.
Remove installed package / application · Publisher instructions
npm uninstall -g claude-cup

Official Documentation & Sources

What it does

Claude Cup provides terminal/browser dashboards for Claude Code activity, usage metrics and a local MCP/hooks integration.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Tracking Claude Code usage and local developer productivity metrics.

Representative uses

Track edits, prompts, tool calls and token usage
View a local dashboard
Compare usage scores
Enable local productivity/eco features

Limitations

It is a community package, not an Anthropic product.
The reviewed package documents local transcript and credential-pattern analysis, which is privacy-sensitive.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: No service authentication documented for the local dashboard.
Permissions: Reads local Claude Code activity/transcript data and changes local integration settings.
Data handling: The package states data stays in its local directory; credential-pattern checks operate on local metadata.
Cost: free
Risk and cautions: The integration handles local developer transcripts and credential-pattern metadata; review its local storage and dashboard exposure.

Access scope and cautions

Write actions: Register hooks Change local eco-mode settings
Sensitive access: Claude Code transcripts Developer credential-pattern metadata
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Track edits, prompts, tool calls and token usage; View a local dashboard; Compare usage scores; Enable local productivity/eco features.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded endpoint: http://localhost:4690. Recorded transport: stdio. Client notes: Registers local hooks/MCP integration on first launch. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: No service authentication documented for the local dashboard.

Can it modify data or perform write operations?

Documented write actions include: Register hooks; Change local eco-mode settings. Recorded permission boundary: Reads local Claude Code activity/transcript data and changes local integration settings.

What data-handling boundary should I consider?

The package states data stays in its local directory; credential-pattern checks operate on local metadata. Recorded sensitive-access context: Claude Code transcripts; Developer credential-pattern metadata.

What limitations and risks should I check before use?

The integration handles local developer transcripts and credential-pattern metadata; review its local storage and dashboard exposure. It is a community package, not an Anthropic product. The reviewed package documents local transcript and credential-pattern analysis, which is privacy-sensitive. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Community package is listed as Community implementation in MCP100’s current evidence.