# Life Dashboard (oci · ghcr.io/owen282000/life-dashboard-mcp)

Read-only health and screen time history from the Postgres of a self-hosted Life Dashboard Stack

- Trust score: 58/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/owen282000/life-dashboard-mcp`: 58/100 (this document), [markdown](https://verifymcp.io/servers/owen282000-life-dashboard/ghcr-io-owen282000-life-dashboard-mcp.md), [page](https://verifymcp.io/servers/owen282000-life-dashboard/ghcr-io-owen282000-life-dashboard-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/owen282000/life-dashboard-mcp`
- Version: `1.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-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to owen282000/life-dashboard-stack).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1654 tokens (~206/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 Life Dashboard MCP server?

Life Dashboard runs locally as a container image, launched with docker run --rm -i -e MCP_TRANSPORT -e PGHOST -e PGDATABASE -e PGUSER -e PGPASSWORD ghcr.io/owen282000/life-dashboard-mcp:1.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add owen282000-life-dashboard -- docker run --rm -i -e MCP_TRANSPORT -e PGHOST -e PGDATABASE -e PGUSER -e PGPASSWORD ghcr.io/owen282000/life-dashboard-mcp:1.2.1
```

This image reads MCP_TRANSPORT, PGHOST, PGDATABASE, PGUSER and PGPASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "owen282000-life-dashboard": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "PGHOST",
        "-e",
        "PGDATABASE",
        "-e",
        "PGUSER",
        "-e",
        "PGPASSWORD",
        "ghcr.io/owen282000/life-dashboard-mcp:1.2.1"
      ]
    }
  }
}
```

This image reads MCP_TRANSPORT, PGHOST, PGDATABASE, PGUSER and PGPASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "owen282000-life-dashboard": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "PGHOST",
        "-e",
        "PGDATABASE",
        "-e",
        "PGUSER",
        "-e",
        "PGPASSWORD",
        "ghcr.io/owen282000/life-dashboard-mcp:1.2.1"
      ]
    }
  }
}
```

This image reads MCP_TRANSPORT, PGHOST, PGDATABASE, PGUSER and PGPASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add owen282000-life-dashboard -- docker run --rm -i -e MCP_TRANSPORT -e PGHOST -e PGDATABASE -e PGUSER -e PGPASSWORD ghcr.io/owen282000/life-dashboard-mcp:1.2.1
```

This image reads MCP_TRANSPORT, PGHOST, PGDATABASE, PGUSER and PGPASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "owen282000-life-dashboard": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "PGHOST",
        "-e",
        "PGDATABASE",
        "-e",
        "PGUSER",
        "-e",
        "PGPASSWORD",
        "ghcr.io/owen282000/life-dashboard-mcp:1.2.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads MCP_TRANSPORT, PGHOST, PGDATABASE, PGUSER and PGPASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  owen282000-life-dashboard:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "MCP_TRANSPORT", "-e", "PGHOST", "-e", "PGDATABASE", "-e", "PGUSER", "-e", "PGPASSWORD", "ghcr.io/owen282000/life-dashboard-mcp:1.2.1"]
```

This image reads MCP_TRANSPORT, PGHOST, PGDATABASE, PGUSER and PGPASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "owen282000-life-dashboard": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "PGHOST",
        "-e",
        "PGDATABASE",
        "-e",
        "PGUSER",
        "-e",
        "PGPASSWORD",
        "ghcr.io/owen282000/life-dashboard-mcp:1.2.1"
      ]
    }
  }
}
```

This image reads MCP_TRANSPORT, PGHOST, PGDATABASE, PGUSER and PGPASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "owen282000-life-dashboard": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "PGHOST",
        "-e",
        "PGDATABASE",
        "-e",
        "PGUSER",
        "-e",
        "PGPASSWORD",
        "ghcr.io/owen282000/life-dashboard-mcp:1.2.1"
      ]
    }
  }
}
```

This image reads MCP_TRANSPORT, PGHOST, PGDATABASE, PGUSER and PGPASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## 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-11-05 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 56, 0)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.47 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.2.0 → 1.2.1

### 2026-10-31 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `list_phones` (~65 tokens)

List the phones that send data to this stack: label, platforms (Android, iPhone,
Screen time), device, app version, when it last sent data, and the first and last day
with data. Also gives the time zone and today's date. Call this first.

### `data_catalog` (~189 tokens)

What each phone has stored and what the other tools can answer from it. Per phone:
every type of data (the payload key, such as heart_rate or sleep) with its records,
windows (series sent per time window), the apps that wrote it (sources), its first and
last local day, and read=false when no tool reads it (the dashboards still show it).
tools gives, per tool, what has data: the daily_summary fields, the day range of
sleep_nights, workouts and screen_time (null when there is none), and every trend metric
with its day range. Steps per day come from daily_totals, so raw steps records show
read=false. Call it before asking for a metric, to know whether and since when it
exists.

Input parameters:

- `phone`: A phone label from list_phones, such as pixel. Leave it out for every phone.

### `sync_status` (~213 tokens)

When each phone last sent data and when each type of data last arrived. Per phone:
payload_sources (Android, iPhone or Screen time) with the last payload, hours since,
payloads in the last 24 hours and app version; types with last_time (the newest
record), last_received (when the receiver last stored any of it), days_since,
active_days (local days with data in the 28 days up to the newest record),
usual_gap_days (28, or fewer for a younger type, divided by active_days) and quiet;
sources: per type and writing app, its newest record and whether it went quiet. quiet
means the newest record is older than twice the usual gap; null when the type had data
on one day only. A source is quiet by the same rule when it wrote the type in those 28
days. quiet lists the quiet types.

Input parameters:

- `phone`: A phone label from list_phones, such as pixel. Leave it out for every phone.

### `daily_summary` (~173 tokens)

Totals per day, one row per phone and day: steps, distance_km, active_kcal,
total_kcal, sleep_h and in_bed_h (the night that ended that morning), exercise_min and
workouts, screen_min (Android only), resting_hr (bpm) and weight_kg. Steps, distance
and calories are the phone's daily totals, counted once across phone and watch. null
means nothing was recorded. complete=false marks today, a running total. Dates are
inclusive, at most 92 days per call.

Input parameters:

- `from_date` (string, required): A date as YYYY-MM-DD
- `phone`: A phone label from list_phones, such as pixel. Leave it out for every phone.
- `to_date` (string, required): A date as YYYY-MM-DD

### `sleep_nights` (~156 tokens)

One night per phone, on the date the person woke up: bedtime and wake_time (local
time), asleep_h, in_bed_h, deep_h, light_h, rem_h and awake_h (stages are null when the
night has none), hr_low (the lowest 10-minute average heart rate in the night, not the
resting heart rate) and hr_avg. Dates are wake dates, inclusive, at most 92 days per
call.

Input parameters:

- `from_date` (string, required): A date as YYYY-MM-DD
- `phone`: A phone label from list_phones, such as pixel. Leave it out for every phone.
- `to_date` (string, required): A date as YYYY-MM-DD

### `workouts` (~124 tokens)

Every workout: day, start_time and end_time (local time), activity (such as running,
walking or biking), minutes and the app that recorded it. A workout that a watch and a
phone app both recorded is listed once. Dates are inclusive, at most 92 days and 100
workouts per call.

Input parameters:

- `from_date` (string, required): A date as YYYY-MM-DD
- `phone`: A phone label from list_phones, such as pixel. Leave it out for every phone.
- `to_date` (string, required): A date as YYYY-MM-DD

### `trend` (~442 tokens)

One metric over the last `days` complete days (up to yesterday) against the same
number of days before: mean, lowest and highest day, days with data, and the change of
the mean (absolute and in percent). For exercise_min a day without a workout counts as
0 in the mean; for every other metric the mean is over days with data.

Input parameters:

- `days` (integer): Length of the period in days, 7 to 365
- `metric` (string, required): What to measure: steps (steps): Steps per day, counted once across phone and watch; distance_km (km): Distance per day; active_kcal (kcal): Active energy per day; total_kcal (kcal): Total energy per…
- `phone`: A phone label from list_phones, such as pixel. Leave it out for every phone.

### `screen_time` (~102 tokens)

Screen time on one day per phone: total_min, the number of apps, the last use, and
the top 10 apps with their minutes. The day is the app's day, which runs from 04:00 to
04:00 by default. Android phones only.

Input parameters:

- `date` (string, required): A date as YYYY-MM-DD
- `phone`: A phone label from list_phones, such as pixel. Leave it out for every phone.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/owen282000-life-dashboard/ghcr-io-owen282000-life-dashboard-mcp#diagnostics

## Score history

- 2026-11-05: 58
- 2026-11-04: 57
- 2026-11-03: 57
- 2026-11-02: 56
- 2026-11-01: 56
- 2026-10-31: 56
- 2026-10-30: 55
- 2026-10-29: 55
- 2026-10-28: 54
- 2026-10-27: 54
- 2026-10-26: 53
- 2026-10-25: 53
- 2026-10-24: 52
- 2026-10-23: 52
- 2026-10-22: 51
- 2026-10-21: 51
- 2026-10-20: 50
- 2026-10-19: 50
- 2026-10-18: 49
- 2026-10-17: 48

## Common questions

### What is the Life Dashboard MCP server?

Life Dashboard is an MCP server listed in the public MCP registry as io.github.owen282000/life-dashboard. Read-only health and screen time history from the Postgres of a self-hosted Life Dashboard Stack. This page covers its container image (ghcr.io/owen282000/life-dashboard-mcp).

### Is the Life Dashboard MCP server safe to use?

Life Dashboard scores 58 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 Life Dashboard MCP server expose?

Life Dashboard exposes 8 tools: list_phones, data_catalog, sync_status, daily_summary, sleep_nights, and 3 more. Their descriptions and schemas cost roughly 1,464 tokens of context every time the server is loaded.

### Is the Life Dashboard MCP server still maintained?

Life Dashboard is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Life Dashboard MCP server under?

Life 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

- GitHub Container Registry: https://ghcr.io/owen282000/life-dashboard-mcp
- Repository: https://github.com/owen282000/life-dashboard-stack
- Website: https://github.com/owen282000/life-dashboard-stack/blob/main/docs/mcp.md
- Changelog RSS feed: https://verifymcp.io/servers/owen282000-life-dashboard/ghcr-io-owen282000-life-dashboard-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/owen282000-life-dashboard/ghcr-io-owen282000-life-dashboard-mcp.json
- HTML version of this page: https://verifymcp.io/servers/owen282000-life-dashboard/ghcr-io-owen282000-life-dashboard-mcp