# WidgetDash (npm · widgetdash-mcp)

Push any number to your iPhone Home Screen / Lock Screen widgets and Live Activities.

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

## Components

- npm · `widgetdash-mcp`: 72/100 (this document), [markdown](https://verifymcp.io/servers/purian-widgetdash-mcp/widgetdash-mcp.md), [page](https://verifymcp.io/servers/purian-widgetdash-mcp/widgetdash-mcp)

## Channel facts

- Registry: `npm`
- Package: `widgetdash-mcp`
- Version: `0.2.0`
- 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**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 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 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1201 tokens (~240/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the WidgetDash MCP server?

WidgetDash runs locally as an npm package, launched with npx -y widgetdash-mcp. 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 purian-widgetdash-mcp -- npx -y widgetdash-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "purian-widgetdash-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "widgetdash-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "purian-widgetdash-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "widgetdash-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add purian-widgetdash-mcp -- npx -y widgetdash-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "purian-widgetdash-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "widgetdash-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add purian-widgetdash-mcp --command npx --arg -y --arg widgetdash-mcp
```

### Hermes

```yaml
mcp_servers:
  purian-widgetdash-mcp:
    command: "npx"
    args: ["-y", "widgetdash-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "purian-widgetdash-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "widgetdash-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add purian-widgetdash-mcp -t stdio -c npx -a -y widgetdash-mcp
```

### Other

```json
{
  "mcpServers": {
    "purian-widgetdash-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "widgetdash-mcp"
      ]
    }
  }
}
```

## 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 72, +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-11-03 (score 71, +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.

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

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

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

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

### 2026-10-28 (score 68)

First indexed and scored.

## MCP tools (5)

### `push_metrics` (~391 tokens)

Push metrics to iPhone widget

Create or update a WidgetDash data source shown on the user's iPhone Home Screen / Lock Screen widgets and Live Activities. Sets the source's title, SF Symbol icon, category and its full list of metrics (label + value + type + color). The metrics list REPLACES the source's current metrics; use push_number to change a single value. Omitted display_name/icon/category keep their current values; sort_order only applies when the source is created. Requires WIDGETDASH_WRITE_KEY.

Input parameters:

- `category` (string): Free-form grouping, e.g. 'finance', 'monitoring', 'fitness'. If omitted, keeps the existing category (default 'general').
- `display_name` (string): Title shown on the widget, e.g. 'Stripe'. If omitted, keeps the existing name (or derives one from source_key for new sources).
- `icon` (string): SF Symbol name shown next to the title, e.g. 'dollarsign.circle.fill', 'chart.bar.fill', 'server.rack', 'heart.fill', 'cart.fill'. If omitted, keeps the existing icon (default 'circle.fill').
- `metrics` (array, required): Metrics to show, in display order. Small widgets show the first few, so put the most important first.
- `raw_data` (object): Optional arbitrary JSON object stored alongside the metrics (not shown on the widget). If omitted, existing raw_data is kept.
- `sort_order` (integer): Position for a NEW source among your sources (lower first, default 0). Ignored when updating an existing source: its order is set in the WidgetDash app.
- `source_key` (string, required): Stable identifier for this data source, e.g. 'stripe_mrr' or 'server_health'. Lowercase letters, digits, '_' or '-'. Pushing to an existing key updates it; a new key creates a new widget source.

### `push_number` (~455 tokens)

Push one number to iPhone widget

Quickest way to put a single number or value on the user's iPhone Home Screen / Lock Screen widget via WidgetDash, e.g. 'Stripe MRR = $12,400' or 'Open tickets = 7'. Sets one metric (matched by label) on a source, keeping the source's other metrics, title and icon; creates the source if it does not exist. Requires WIDGETDASH_WRITE_KEY.

Input parameters:

- `category` (string): Free-form grouping, e.g. 'finance', 'monitoring', 'fitness'. If omitted, keeps the existing category (default 'general').
- `color` (string): Optional accent color (green/red/yellow/blue/gray/orange/purple/cyan); defaults to the existing metric's color.
- `display_name` (string): Title shown on the widget, e.g. 'Stripe'. If omitted, keeps the existing name (or derives one from source_key for new sources).
- `icon` (string): SF Symbol name shown next to the title, e.g. 'dollarsign.circle.fill', 'chart.bar.fill', 'server.rack', 'heart.fill', 'cart.fill'. If omitted, keeps the existing icon (default 'circle.fill').
- `label` (string, required): Short label shown on the widget, e.g. 'MRR' or 'Users online'.
- `sort_order` (integer): Position for a NEW source among your sources (lower first, default 0). Ignored when updating an existing source: its order is set in the WidgetDash app.
- `source_key` (string, required): Stable identifier for this data source, e.g. 'stripe_mrr' or 'server_health'. Lowercase letters, digits, '_' or '-'. Pushing to an existing key updates it; a new key creates a new widget source.
- `type` (string): Optional; defaults to the existing metric's type, else inferred from the value.
- `value` (required): The value to display, pre-formatted as you want it shown (e.g. '$12,400', '42', 'Healthy'). For 'progress' use 0-100; for 'timestamp' an ISO 8601 time or Unix epoch seconds.

### `list_sources` (~66 tokens)

List WidgetDash sources

List the data sources on the user's WidgetDash iPhone widgets (source_key, title, icon, enabled/hidden) plus the plan's source usage (the free plan allows 5 sources). Uses WIDGETDASH_READ_KEY, or the write key if no read key is set.

### `get_widget_data` (~85 tokens)

Read iPhone widget data

Read what is currently shown on the user's WidgetDash iPhone widgets: every enabled source with its metrics and last update time, or one source if source_key is given. Uses WIDGETDASH_READ_KEY, or the write key if no read key is set.

Input parameters:

- `source_key` (string): Only return this source. Omit to return all sources shown on the widget.

### `delete_source` (~71 tokens)

Delete WidgetDash source

Permanently delete a data source (and its data) from the user's WidgetDash iPhone widgets. Ends any Live Activity for it. Only do this when the user asks to remove it. Requires WIDGETDASH_WRITE_KEY.

Input parameters:

- `source_key` (string, required): The source_key to delete (see list_sources).

## Diagnostics

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

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 68

## Common questions

### What is the WidgetDash MCP server?

WidgetDash is an MCP server listed in the public MCP registry as io.github.purian/widgetdash-mcp. Push any number to your iPhone Home Screen / Lock Screen widgets and Live Activities. This page covers its npm package (widgetdash-mcp).

### Is the WidgetDash MCP server safe to use?

WidgetDash scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 WidgetDash MCP server expose?

WidgetDash exposes 5 tools: push_metrics, push_number, list_sources, get_widget_data, delete_source. Their descriptions and schemas cost roughly 1,068 tokens of context every time the server is loaded.

### Is the WidgetDash MCP server still maintained?

WidgetDash 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 WidgetDash MCP server under?

WidgetDash 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

- npm package: https://www.npmjs.com/package/widgetdash-mcp
- Socket report: https://socket.dev/npm/package/widgetdash-mcp
- Repository: https://github.com/purian/widgetdash-mcp
- Website: https://widgetdash.app/
- Changelog RSS feed: https://verifymcp.io/servers/purian-widgetdash-mcp/widgetdash-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/purian-widgetdash-mcp/widgetdash-mcp.json
- HTML version of this page: https://verifymcp.io/servers/purian-widgetdash-mcp/widgetdash-mcp