Ext Ops Panel
Open dashboard
Comparison

TraceMe vs HarnessScope

TraceMe is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.

TraceMe is a plugin bundle for AI coding tools published by linxu. No marketplace we read lists it any more. HarnessScope is an MCP server published by moongioh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceTraceMeHarnessScope
Community marketplace dawnever/cc-market Removed on 2026-10-17
Version: 0.3.40
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.3
Downloads/month (npm): 112
Downloads/week (npm): 13
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

TraceMe vs HarnessScope
FactTraceMeno longer listed · HarnessScope
Marketplaces that list it (differs)01
Stars (GitHub) (differs)31
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (hscope)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)3Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/dawnever/cc-marketgithub.com/moongioh/harness-scope
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of TraceMe

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • dash0

    OpenTelemetry observability for Claude Code sessions. Captures tool calls, LLM invocations, token usage, and errors as OTel traces. Send telemetry to Dash0 or any…

    by dash0hq · Plugin bundle

    Listed on: Claude Code: claude-plugins-official, Claude Code: claude-plugins-community · Describes nearly the same job

  • session-metrics

    Per-turn token, cost, and cache analytics for Claude Code sessions. Multi-format export (text/JSON/CSV/MD/HTML) with session blocks, weekly roll-up, subagent attribution…

    by George Liu · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • observability

    Local usage board for Claude Code. A hooks module records one metadata row per turn (exact engine cost, tokens by model, tool calls, agent spawns, context fill, rate-limit…

    by Eigenwise · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • trajectory

    Turnkey observability for AI coding agents - captures sessions and exports to Datadog LLM Observability

    by Datadog · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • ccam-analytics

    Deep analytics and monitoring for Claude Code sessions — cost tracking, token usage breakdowns, usage trends, and productivity scoring powered by Agent Monitor.

    by Son Nguyen · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • session-report

    Generate an explorable HTML report of Claude Code session usage — tokens, cache efficiency, subagents, skills, and the most expensive prompts — from local ~/.claude/projects…

    by Anthropic · Plugin bundle

    Listed on: Claude Code: claude-plugins-official · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

TraceMe

In its own words, on Community GitHub marketplaces:

[Archived] Local-first personal observability for Claude Code — token usage, cost, tool usage, daily reports. Hooks capture session/tool/prompt data, transcript parser extracts token/cost.

HarnessScope

In its own words, on Official MCP Registry:

Turn-level governance observability for Claude Code transcripts. Local-first, no LLM inside.

How to run each

TraceMe

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

HarnessScope As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio hscope -- npx -y hscope mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of TraceMe publish no settings it asks for, so we do not compare settings.

What it can do: TraceMe · What it can do: HarnessScope · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built