# RunGlance (npm · @openly-useful/runglance-mcp)

Read-only local progress, usage, lock state, work lists, and verified run receipts.

- Trust score: 87/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `@openly-useful/runglance-mcp`: 87/100 (this document), [markdown](https://verifymcp.io/servers/org-openlyuseful-runglance/openly-useful-runglance-mcp.md), [page](https://verifymcp.io/servers/org-openlyuseful-runglance/openly-useful-runglance-mcp)

## Channel facts

- Registry: `npm`
- Package: `@openly-useful/runglance-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-09-21.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 28 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 361 tokens (~72/item across 5 items; 4 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - 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 current MCP spec version (2026-07-28).

## Install

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

RunGlance runs locally as an npm package, launched with npx -y @openly-useful/runglance-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 org-openlyuseful-runglance -- npx -y @openly-useful/runglance-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "org-openlyuseful-runglance": {
      "command": "npx",
      "args": [
        "-y",
        "@openly-useful/runglance-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-openlyuseful-runglance": {
      "command": "npx",
      "args": [
        "-y",
        "@openly-useful/runglance-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add org-openlyuseful-runglance -- npx -y @openly-useful/runglance-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-openlyuseful-runglance": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@openly-useful/runglance-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-openlyuseful-runglance --command npx --arg -y --arg @openly-useful/runglance-mcp
```

### Hermes

```yaml
mcp_servers:
  org-openlyuseful-runglance:
    command: "npx"
    args: ["-y", "@openly-useful/runglance-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "org-openlyuseful-runglance": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@openly-useful/runglance-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-openlyuseful-runglance -t stdio -c npx -a -y @openly-useful/runglance-mcp
```

### Other

```json
{
  "mcpServers": {
    "org-openlyuseful-runglance": {
      "command": "npx",
      "args": [
        "-y",
        "@openly-useful/runglance-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-09-21 (score 87, +1)

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

### 2026-09-19 (score 86, +1)

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

### 2026-09-17 (score 85, +1)

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

### 2026-09-15 (score 84, +1)

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

### 2026-09-12 (score 83, +1)

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

### 2026-09-10 (score 82, +1)

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

### 2026-09-08 (score 81, +1)

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

### 2026-09-06 (score 80, +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.

## MCP tools (4)

### `runglance_get_status` (~56 tokens)

Get RunGlance Status

Read the latest local RunGlance snapshot. Returns thread state, progress, active counts, usage truth classes, explicit lock state, freshness, capabilities, and the bounded final receipt. It never calculates project readiness or writes activity.

Output parameters:

- `capabilities` (object)
- `counts` (object)
- `freshness` (object)
- `generatedAt` (string)
- `lastReceipt`
- `lock` (object)
- `ok` (boolean)
- `progress` (object)
- `schemaVersion` (integer)
- `sessionId`
- `thread` (object)
- `usage` (object)

### `runglance_list_work` (~122 tokens)

List RunGlance Work

List bounded, redacted RunGlance thread, workflow, skill, agent, and tool activity. Defaults to active work and supports finished/all scope, exact filters, and offset pagination.

Input parameters:

- `kind` (string): Optional exact entity-kind filter.
- `limit` (integer): Maximum work items to return, from 1 through 100.
- `offset` (integer): Number of matching work items to skip.
- `scope` (string): Select active work, terminal finished work, or both.
- `state` (string): Optional exact lifecycle-state filter.

Output parameters:

- `count` (integer)
- `hasMore` (boolean)
- `nextOffset`
- `offset` (integer)
- `ok` (boolean)
- `scope` (string)
- `total` (integer)
- `work` (array)

### `runglance_get_usage` (~48 tokens)

Get RunGlance Usage

Read context, provider-quota, and task-budget remaining percentages from RunGlance. Every metric preserves exact, derived, estimated, or unknown truth and never substitutes zero for unavailable data.

Output parameters:

- `generatedAt` (string)
- `ok` (boolean)
- `usage` (object)

### `runglance_get_locks` (~41 tokens)

Get RunGlance Locks

Read the bounded, redacted RunGlance lock observation. Stale, unknown, and unlocked are distinct states; silence never becomes a lock.

Output parameters:

- `count` (integer)
- `generatedAt` (string)
- `locks` (array)
- `ok` (boolean)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/org-openlyuseful-runglance/openly-useful-runglance-mcp#diagnostics

## Score history

- 2026-09-21: 87
- 2026-09-20: 86
- 2026-09-19: 86
- 2026-09-18: 85
- 2026-09-17: 85
- 2026-09-16: 84
- 2026-09-15: 84
- 2026-09-14: 83
- 2026-09-13: 83
- 2026-09-12: 83
- 2026-09-11: 82
- 2026-09-10: 82
- 2026-09-09: 81
- 2026-09-08: 81
- 2026-09-07: 80
- 2026-09-06: 80
- 2026-09-05: 79
- 2026-09-04: 79
- 2026-09-03: 78
- 2026-09-02: 78
- 2026-09-01: 77
- 2026-08-31: 77
- 2026-08-30: 73
- 2026-08-29: 73
- 2026-08-28: 73
- 2026-08-27: 73
- 2026-08-26: 73
- 2026-08-25: 72
- 2026-08-24: 72
- 2026-08-23: 72

## Common questions

### What is the RunGlance MCP server?

RunGlance is an MCP server listed in the public MCP registry as org.openlyuseful/runglance. Read-only local progress, usage, lock state, work lists, and verified run receipts. This page covers its npm package (@openly-useful/runglance-mcp).

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

RunGlance scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 RunGlance MCP server expose?

RunGlance exposes 4 tools: runglance_get_status, runglance_list_work, runglance_get_usage, runglance_get_locks. Their descriptions and schemas cost roughly 267 tokens of context every time the server is loaded.

### Is the RunGlance MCP server still maintained?

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

RunGlance declares the Apache-2.0 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/@openly-useful/runglance-mcp
- Socket report: https://socket.dev/npm/package/@openly-useful/runglance-mcp
- Repository: https://github.com/Openly-Useful/project-status
- Changelog RSS feed: https://verifymcp.io/servers/org-openlyuseful-runglance/openly-useful-runglance-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-openlyuseful-runglance/openly-useful-runglance-mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-openlyuseful-runglance/openly-useful-runglance-mcp