Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Task tracking (sessions, ETA, dashboard)

PYPI · MCP-TRACKING · SCANNED SEP 24

Track long-running tasks in real time: sessions, steps, speed, ETA, HTTP API and TUI dashboard.

Available components

pypi · mcp-tracking 51
51 Trust /100
Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 2 of 36 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 845 tokens (~70/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "tracking_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

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 Task tracking (sessions, ETA, dashboard) MCP server?

Task tracking (sessions, ETA, dashboard) runs locally as a PyPI package, launched with uvx mcp-tracking. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-tracking

# add to Claude Code
claude mcp add amineutron-mcp-tracking -- uvx mcp-tracking
// .cursor/mcp.json
{
  "mcpServers": {
    "amineutron-mcp-tracking": {
      "command": "uvx",
      "args": [
        "mcp-tracking"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "amineutron-mcp-tracking": {
      "command": "uvx",
      "args": [
        "mcp-tracking"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add amineutron-mcp-tracking -- uvx mcp-tracking
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "amineutron-mcp-tracking": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-tracking"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add amineutron-mcp-tracking --command uvx --arg mcp-tracking
# ~/.hermes/config.yaml
mcp_servers:
  amineutron-mcp-tracking:
    command: "uvx"
    args: ["mcp-tracking"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "amineutron-mcp-tracking": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-tracking"
      ]
    }
  }
}
# add to Vellum
assistant mcp add amineutron-mcp-tracking -t stdio -c uvx -a mcp-tracking
// mcp.json
{
  "mcpServers": {
    "amineutron-mcp-tracking": {
      "command": "uvx",
      "args": [
        "mcp-tracking"
      ]
    }
  }
}
Changelog

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.

  • 24 Sept 26 51

    First indexed and scored.

Diagnostics

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 24 Sept 2026 · Analysed pypi/mcp-tracking@0.2.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 36 packages
Packages resolved 36
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~845 tokens

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 →

Tool Tokens
open_tracking_ui ~60

Ouvre le dashboard de tracking dans un terminal Kitty. Args: filter_template: Template a afficher au demarrage ("lyra_task", "movie", "download"...) Si absent, affiche toutes les sessions.

NameTypeReqDescription
filter_template–––
NameTypeReqDescription
resultstringyes–

No examples provided.

tracking_complete ~36

Marque une session comme terminee et met la progression a 100%.

NameTypeReqDescription
message–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

tracking_create ~204

Cree une nouvelle session de tracking. Args: name: Nom de la session (ex: "[DEV] Build worldmonitor") template: voir tracking_templates() ("free", "machine", "download", "lyra_task"...) total: Valeur totale (ex: 15300 pour 15300 MB, 6 pour 6 etapes) unit: Unite affichee (ex: " MB", " etapes") items: Liste optionnelle d'etapes [{name, status?, total?, unit?, note?}] extra: Champs specifiques au template (speed, eta, operation, target...) pid: PID du processus a signaler par tracking_stop / tracking_kill

NameTypeReqDescription
extra–––
items–––
namestringyes–
pid–––
templatestringyes–
totalnumberyes–
unitstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

tracking_delete ~26

Supprime une session (sans toucher au processus).

NameTypeReqDescription
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

tracking_error ~30

Marque une session en erreur.

NameTypeReqDescription
messagestringyes–
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

tracking_get ~32

Retourne l'etat formate complet d'une session (avec metriques).

NameTypeReqDescription
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

tracking_kill ~57

Arret force : envoie SIGKILL au processus si la session a un `pid`, puis supprime la session du dashboard. Args: session_id: ID de la session

NameTypeReqDescription
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

tracking_list ~75

Liste les sessions avec filtres optionnels. Args: template: Filtrer par template ("download", "machine", "free", "movie", "lyra_task"...) status: Filtrer par statut ("running", "done", "error", "paused")

NameTypeReqDescription
status–––
template–––
NameTypeReqDescription
resultstringyes–

No examples provided.

tracking_log ~48

Ajoute une entree de log (info | warn | error) sans modifier la progression.

NameTypeReqDescription
levelstring––
messagestringyes–
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

tracking_stop ~81

Arret propre : envoie SIGTERM au processus si la session a un `pid`, puis marque la session 'paused' (elle reste visible dans le dashboard). Args: session_id: ID de la session message: Raison de l'arret (optionnel)

NameTypeReqDescription
message–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

tracking_templates ~23

Liste les templates disponibles (builtins + ~/.config/tracking/templates.json).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

tracking_update ~173

Met a jour la progression d'une session. La vitesse, l'ETA et le temps ecoule sont calcules automatiquement a partir de `processed`. Args: session_id: ID de la session processed: Nouvelle valeur de progression (optionnel) message: Message de log a ajouter (optionnel) item_updates: Etapes a mettre a jour ou creer [{name?, id?, status?, processed?, note?}] extra: Champs extra a mettre a jour (speed, eta, phase...) level: Niveau du message : "info" | "warn" | "error"

NameTypeReqDescription
extra–––
item_updates–––
levelstring––
message–––
processed–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the Task tracking (sessions, ETA, dashboard) MCP server?

Task tracking (sessions, ETA, dashboard) is an MCP server listed in the public MCP registry as io.github.amineutron/mcp-tracking. Track long-running tasks in real time: sessions, steps, speed, ETA, HTTP API and TUI dashboard. This page covers its PyPI package (mcp-tracking).

Is the Task tracking (sessions, ETA, dashboard) MCP server safe to use?

Task tracking (sessions, ETA, dashboard) scores 51 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. 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 Task tracking (sessions, ETA, dashboard) MCP server expose?

Task tracking (sessions, ETA, dashboard) exposes 12 tools: tracking_create, tracking_update, tracking_log, tracking_complete, tracking_error, and 7 more. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.

Is the Task tracking (sessions, ETA, dashboard) MCP server still maintained?

Task tracking (sessions, ETA, dashboard) is still listed as active in the MCP registry. We last reached this channel on 24 September 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 Task tracking (sessions, ETA, dashboard) MCP server under?

Task tracking (sessions, ETA, dashboard) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.