Project Status MCP server

by openlyuseful.org·org.openlyuseful/project-status·v1.2.1

No reviews yet

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

B74/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B74/100

full report

Adoption

New

0 stars39 downloads/wk

Reviews

Write one

Nobody has reviewed Project Status yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Project Status tools (12)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

project_status_get_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.
project_status_get_dependencies
Read blocking and informing relationships from the validated task DAG. Optionally focus upstream or downstream of one task and paginate the result.
project_status_get_locks
Read the bounded, redacted local thread-lock observation. A stale or unknown observation is not reported as unlocked.
project_status_get_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.
project_status_get_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.
project_status_list_active_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.
project_status_list_tasks
List validated manifest tasks with optional status and phase filters plus bounded offset pagination. Returns public task details and no local evidence locators.
project_status_validate_manifest
Read and validate the configured manifest against the canonical core contract. Returns bounded field-level errors without changing the manifest.
runglance_get_locks
Read the bounded, redacted RunGlance lock observation. Stale, unknown, and unlocked are distinct states; silence never becomes a lock.
runglance_get_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.
runglance_get_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.
runglance_list_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.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

1 medium

Code scan3 source files scanned20/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 55 days ago12/15
Maintainer identitynamespace and repository owner differ4/10

Findings (1)

mediumeval / new Function usedexec.eval

dist/index.js: …ourceCode, sch); const validate = new Function(`${names_1.default.self}`, `${names_1.de…

Overall 74/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Project Status compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 74/100; higher than 40% of 48,255 servers
Tools: 12; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break
Downloads a week: 39; more than 30% of 12,191 servers with a package

What its tools let an agent do: 8 read · 4 run or deploy

Install Project Status in Claude Code, Cursor or VS Code

Runs npx -y @openly-useful/project-status-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add project-status -- npx -y @openly-useful/project-status-mcp

Add to Cursor

What the publisher says

From the Project Status repository's README, as published. We do not edit it. Read it on GitHub

StatusGlance

StatusGlance is Openly Useful's visibility family: StatusGlance / Readiness turns one repository-local manifest into evidence-backed delivery readiness; StatusGlance / RunGlance shows observed run activity without model polling. Both are portable across Claude, OpenAI/Codex, and generic CLIs, with optional bounded read-only MCP entrypoints.

This compatibility-first branding release retains the project-status and runglance plugin IDs, npm/MCP names, commands, storage paths, repository URL, and Apache-2.0 license. Existing integrations do not need a rename migration. A status request reads existing evidence once; it does not start work, verification, monitoring, or installation.

The delivery loop

Conductor Swarm owns execution: observe changes → shape coherent work → run ready independent lanes in parallel → verify and integrate at milestones → adapt → continue authorized work or finish. Pickup repairs missing context; Continuity handles actual transfers. These are complementary tools, not mandatory extra agents or serialized stages. Agent Workflow Swarms defines the execution framework.

StatusGlance observes that loop. Use existing host events, task IDs, and milestone evidence. No event stream means unknown activity. A local setup file does not prove host installation or connection. Repeated revisions call for an approach change within authorized execution, not an ever-growing review loop. Operations Pulse remains the opt-in recurring operations sibling; Skill Feedback Engine proposes durable improvements only when requested.

Alpha, Beta, and Live readiness

The optional versioned delivery extension references existing manifest tasks. Ordered stage scopes accumulate accepted work once; each shows its own denominator, remaining tasks and milestones, next integrated milestone, and acceptance gaps. Empty scope remains unknown. Current stage acceptance requires qualifying evidence and cleared gates; implementation progress and historical weighted credit remain separate.

The bundled dashboard is a historical demonstration, not evidence of any user's current product readiness. Configure and validate real product scope before claiming Alpha, Beta, or Live completion.

This repository contains eight related deliverables:

the canonical portable skill at skill/project-status;
the standalone RunGlance skill at skill/runglance;
the dependency-free RunGlance runtime, host adapters, HUD presets, verification runner, and final receipts;
optional read-only Project Status and RunGlance MCP entrypoints under packages/mcp;
generated OpenAI/Codex and Claude plugin wrappers under plugins/;
deterministic Project Status and RunGlance ZIP distributions produced by scripts/package-skill.mjs and scripts/package-runglance.mjs;
the React/Vite status prototype and its OpenAI Sites worker build.

Trust and safety model

Readiness, evidence validity, live health, and delivery activity remain separate signals. Browser refreshes do not count as monitoring. Read-only inspection is the default; manifest edits, scheduling, installation, publishing, deployment, commits, and remote writes require separate explicit actions.

Activity also separates context-window capacity, provider quota, task budget, monetary cost, progress, heartbeat freshness, and explicit lock ownership. Missing host data stays unknown; it is never displayed as zero or guessed from another metric. Passing verification proves the check and task result recorded by the receipt, not overall project readiness.

Release tooling stays repository-local. It does not install a plugin, change a personal marketplace, publish an archive, create a release, deploy Sites, or write outside its selected artifact directory.

Canonical skill and generated wrappers

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Project Status: common questions

Is Project Status MCP server safe?: Mostly: it is graded B (74/100). Read the Project Status safety report
How do I install Project Status?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Project Status need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Project Status maintained?: The last commit was 57 days ago (2026-09-07). The latest release is v1.2.1.
How does Project Status compare with other MCP servers?: safety score 74/100 (higher than 40% of 48,255 servers); tools 12 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.