# Task tracking (sessions, ETA, dashboard) (pypi · mcp-tracking)

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

- Trust score: 51/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- pypi · `mcp-tracking`: 51/100 (this document), [markdown](https://verifymcp.io/servers/amineutron-mcp-tracking/mcp-tracking.md), [page](https://verifymcp.io/servers/amineutron-mcp-tracking/mcp-tracking)

## Channel facts

- Registry: `pypi`
- Package: `mcp-tracking`
- Version: `0.2.1`
- Transport: `stdio`

## 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-09-24.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 2 of 36 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/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 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 845 tokens (~70/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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 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.

### Claude

```bash
claude mcp add amineutron-mcp-tracking -- uvx mcp-tracking
```

### Cursor

```json
{
  "mcpServers": {
    "amineutron-mcp-tracking": {
      "command": "uvx",
      "args": [
        "mcp-tracking"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "amineutron-mcp-tracking": {
      "command": "uvx",
      "args": [
        "mcp-tracking"
      ]
    }
  }
}
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add amineutron-mcp-tracking --command uvx --arg mcp-tracking
```

### Hermes

```yaml
mcp_servers:
  amineutron-mcp-tracking:
    command: "uvx"
    args: ["mcp-tracking"]
```

### Netclaw

```json
{
  "McpServers": {
    "amineutron-mcp-tracking": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-tracking"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add amineutron-mcp-tracking -t stdio -c uvx -a mcp-tracking
```

### Other

```json
{
  "mcpServers": {
    "amineutron-mcp-tracking": {
      "command": "uvx",
      "args": [
        "mcp-tracking"
      ]
    }
  }
}
```

## 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-09-24 (score 51)

First indexed and scored.

## MCP tools (12)

### `tracking_create` (~204 tokens)

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

Input parameters:

- `extra`
- `items`
- `name` (string, required)
- `pid`
- `template` (string, required)
- `total` (number, required)
- `unit` (string)

Output parameters:

- `result` (string)

### `tracking_update` (~173 tokens)

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"

Input parameters:

- `extra`
- `item_updates`
- `level` (string)
- `message`
- `processed`
- `session_id` (string, required)

Output parameters:

- `result` (string)

### `tracking_log` (~48 tokens)

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

Input parameters:

- `level` (string)
- `message` (string, required)
- `session_id` (string, required)

Output parameters:

- `result` (string)

### `tracking_complete` (~36 tokens)

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

Input parameters:

- `message`
- `session_id` (string, required)

Output parameters:

- `result` (string)

### `tracking_error` (~30 tokens)

Marque une session en erreur.

Input parameters:

- `message` (string, required)
- `session_id` (string, required)

Output parameters:

- `result` (string)

### `tracking_get` (~32 tokens)

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

Input parameters:

- `session_id` (string, required)

Output parameters:

- `result` (string)

### `tracking_list` (~75 tokens)

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")

Input parameters:

- `status`
- `template`

Output parameters:

- `result` (string)

### `tracking_delete` (~26 tokens)

Supprime une session (sans toucher au processus).

Input parameters:

- `session_id` (string, required)

Output parameters:

- `result` (string)

### `tracking_stop` (~81 tokens)

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)

Input parameters:

- `message`
- `session_id` (string, required)

Output parameters:

- `result` (string)

### `tracking_kill` (~57 tokens)

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

Input parameters:

- `session_id` (string, required)

Output parameters:

- `result` (string)

### `tracking_templates` (~23 tokens)

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

Output parameters:

- `result` (string)

### `open_tracking_ui` (~60 tokens)

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.

Input parameters:

- `filter_template`

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/amineutron-mcp-tracking/mcp-tracking#diagnostics

## Score history

- 2026-09-24: 51

## 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.

## Links

- PyPI project: https://pypi.org/project/mcp-tracking/
- Socket report: https://socket.dev/pypi/package/mcp-tracking
- Repository: https://github.com/amineutron/mcp-tracking
- Changelog RSS feed: https://verifymcp.io/servers/amineutron-mcp-tracking/mcp-tracking.xml
- Changelog JSON feed: https://verifymcp.io/servers/amineutron-mcp-tracking/mcp-tracking.json
- HTML version of this page: https://verifymcp.io/servers/amineutron-mcp-tracking/mcp-tracking