# Project Status (npm · @openly-useful/project-status-mcp)

Read-only project readiness, dependency, evidence, and bounded local activity views.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@openly-useful/project-status-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.
  - 0 of 3 dependencies flagged as unhealthy.
- **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**: 86/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 634 tokens (~63/item across 10 items; 8 tools + 2 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**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 Project Status MCP server?

Project Status runs locally as an npm package, launched with npx -y @openly-useful/project-status-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-project-status -- npx -y @openly-useful/project-status-mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "org-openlyuseful-project-status": {
      "command": "npx",
      "args": [
        "-y",
        "@openly-useful/project-status-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-20 (score 86, +1)

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

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

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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-13 (score 83, +1)

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

### 2026-09-11 (score 82, +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-09-09 (score 81, +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. Other categories moved too: Schema Quality & AI Usability fell 1.

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

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

## MCP tools (8)

### `project_status_get_summary` (~46 tokens)

Get Project Status Summary

Read the validated manifest and return its weighted readiness, task totals, audit freshness, gates, time ranges, and critical-path summary. This tool never modifies files or executes monitoring probes.

Output parameters:

- `asOf` (string)
- `audit` (object)
- `criticalPath` (object)
- `gates` (object)
- `initiative` (object)
- `ok` (boolean)
- `score` (object)
- `tasks` (object)
- `time` (object)

### `project_status_validate_manifest` (~32 tokens)

Validate Project Status Manifest

Read and validate the configured manifest against the canonical core contract. Returns bounded field-level errors without changing the manifest.

Output parameters:

- `errorCount` (integer)
- `errors` (array)
- `ok` (boolean)
- `truncated` (boolean)
- `valid` (boolean)

### `project_status_list_tasks` (~87 tokens)

List Project Status Tasks

List validated manifest tasks with optional status and phase filters plus bounded offset pagination. Returns public task details and no local evidence locators.

Input parameters:

- `limit` (integer): Maximum tasks to return (1-100).
- `offset` (integer): Number of matching tasks to skip.
- `phase_id` (string): Optional exact phase identifier.
- `status` (string): Optional task status filter.

Output parameters:

- `count` (number)
- `hasMore` (boolean)
- `nextOffset`
- `offset` (number)
- `ok` (boolean)
- `tasks` (array)
- `total` (number)

### `project_status_get_dependencies` (~87 tokens)

Get Project Status Dependencies

Read blocking and informing relationships from the validated task DAG. Optionally focus upstream or downstream of one task and paginate the result.

Input parameters:

- `direction` (string): Relationship direction relative to task_id.
- `limit` (integer)
- `offset` (integer)
- `task_id` (string): Optional task identifier to focus on.
- `type` (string): Optional dependency type filter.

Output parameters:

- `count` (number)
- `dependencies` (array)
- `hasMore` (boolean)
- `nextOffset`
- `offset` (number)
- `ok` (boolean)
- `taskId`
- `total` (number)

### `project_status_get_activity` (~51 tokens)

Get Project Status Activity

Read the optional local activity snapshot and return its thread state, progress, live counts, usage truth classes, lock, freshness, capabilities, and bounded last verification receipt. No readiness value is calculated or changed.

Output parameters:

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

### `project_status_list_active_work` (~121 tokens)

List Project Status Activity Work

List bounded, redacted workflow, skill, agent, thread, and tool activity. Defaults to active work; scope can include finished work. Supports exact kind/state filters and offset pagination.

Input parameters:

- `kind` (string): Optional exact activity entity kind filter.
- `limit` (integer): Maximum work items to return (1-100).
- `offset` (integer): Number of matching work items to skip.
- `scope` (string): Select currently 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)

### `project_status_get_usage` (~48 tokens)

Get Project Status Usage

Read context, provider-quota, and task-budget remaining percentages from the optional activity snapshot. Each metric preserves exact, derived, estimated, or unknown truth and never substitutes zero for unavailable data.

Output parameters:

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

### `project_status_get_locks` (~33 tokens)

Get Project Status Locks

Read the bounded, redacted local thread-lock observation. A stale or unknown observation is not reported as unlocked.

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-project-status/openly-useful-project-status-mcp#diagnostics

## Score history

- 2026-09-21: 86
- 2026-09-20: 86
- 2026-09-19: 85
- 2026-09-18: 85
- 2026-09-17: 84
- 2026-09-16: 84
- 2026-09-15: 84
- 2026-09-14: 83
- 2026-09-13: 83
- 2026-09-12: 82
- 2026-09-11: 82
- 2026-09-10: 81
- 2026-09-09: 81
- 2026-09-08: 80
- 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 Project Status MCP server?

Project Status is an MCP server listed in the public MCP registry as org.openlyuseful/project-status. Read-only project readiness, dependency, evidence, and bounded local activity views. This page covers its npm package (@openly-useful/project-status-mcp).

### Is the Project Status MCP server safe to use?

Project Status scores 86 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 Project Status MCP server expose?

Project Status exposes 8 tools: project_status_get_summary, project_status_validate_manifest, project_status_list_tasks, project_status_get_dependencies, project_status_get_activity, and 3 more. Their descriptions and schemas cost roughly 505 tokens of context every time the server is loaded.

### Is the Project Status MCP server still maintained?

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

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