Project Status
NPM · @OPENLY-USEFUL/PROJECT-STATUS-MCP
Read-only project readiness, dependency, evidence, and bounded local activity views.
Available components
Last scanned (12 hours ago)
Scores higher than 71% of npm servers
Category Project Management
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. How we score → Why this is hard to score →
Supply Chain Security83
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/server 2.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 74 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 634 tokens (~63/item across 10 items; 8 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 −5
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111770 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed npm/@openly-useful/project-status-mcp@1.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-jm63-cq47-j5jp | CVE-2026-111770 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H | yes |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
project_status_get_activity Get Project Status Activity ~51
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | object | yes | – |
| counts | object | yes | – |
| freshness | object | yes | – |
| generatedAt | string | yes | – |
| lastReceipt | – | yes | – |
| lock | object | yes | – |
| ok | boolean | yes | – |
| progress | object | yes | – |
| schemaVersion | integer | yes | – |
| sessionId | – | yes | – |
| thread | object | yes | – |
| usage | object | yes | – |
No examples provided.
project_status_get_dependencies Get Project Status Dependencies ~87
Read blocking and informing relationships from the validated task DAG. Optionally focus upstream or downstream of one task and paginate the result.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| dependencies | array | yes | – |
| hasMore | boolean | yes | – |
| nextOffset | – | yes | – |
| offset | number | yes | – |
| ok | boolean | yes | – |
| taskId | – | yes | – |
| total | number | yes | – |
No examples provided.
project_status_get_locks Get Project Status Locks ~33
Read the bounded, redacted local thread-lock observation. A stale or unknown observation is not reported as unlocked.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| generatedAt | string | yes | – |
| locks | array | yes | – |
| ok | boolean | yes | – |
No examples provided.
project_status_get_summary Get Project Status Summary ~46
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | – |
| audit | object | yes | – |
| criticalPath | object | yes | – |
| gates | object | yes | – |
| initiative | object | yes | – |
| ok | boolean | yes | – |
| score | object | yes | – |
| tasks | object | yes | – |
| time | object | yes | – |
No examples provided.
project_status_get_usage Get Project Status Usage ~48
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| generatedAt | string | yes | – |
| ok | boolean | yes | – |
| usage | object | yes | – |
No examples provided.
project_status_list_active_work List Project Status Activity Work ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| hasMore | boolean | yes | – |
| nextOffset | – | yes | – |
| offset | integer | yes | – |
| ok | boolean | yes | – |
| scope | string | yes | – |
| total | integer | yes | – |
| work | array | yes | – |
No examples provided.
project_status_list_tasks List Project Status Tasks ~87
List validated manifest tasks with optional status and phase filters plus bounded offset pagination. Returns public task details and no local evidence locators.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| hasMore | boolean | yes | – |
| nextOffset | – | yes | – |
| offset | number | yes | – |
| ok | boolean | yes | – |
| tasks | array | yes | – |
| total | number | yes | – |
No examples provided.
project_status_validate_manifest Validate Project Status Manifest ~32
Read and validate the configured manifest against the canonical core contract. Returns bounded field-level errors without changing the manifest.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| errorCount | integer | yes | – |
| errors | array | yes | – |
| ok | boolean | yes | – |
| truncated | boolean | yes | – |
| valid | boolean | yes | – |
No examples provided.
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.
npm · @openly-useful/project-status-mcp
claude mcp add org-openlyuseful-project-status -- npx -y @openly-useful/project-status-mcp
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 82 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 6 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 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 6 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 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.
What did VerifyMCP test on the Project Status MCP server?
VerifyMCP ran 16 checks on Project Status, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.