RunGlance
NPM · @OPENLY-USEFUL/RUNGLANCE-MCP
Read-only local progress, usage, lock state, work lists, and verified run receipts.
Available components
Last scanned (11 hours ago)
Scores higher than 91% of npm servers
Category Monitoring and Observability
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. 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 Usability87
- 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 361 tokens (~72/item across 5 items; 4 tools + 1 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 26 +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.
- 15 Oct 26 −3
- Stability: pass → 0.80 functional
- 14 Oct 26 0
- Stability: 0.97 → pass security
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/runglance-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 →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
runglance_get_locks Get RunGlance Locks ~41
Read the bounded, redacted RunGlance lock observation. Stale, unknown, and unlocked are distinct states; silence never becomes a lock.
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.
runglance_get_status Get RunGlance Status ~56
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.
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.
runglance_get_usage Get RunGlance Usage ~48
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| generatedAt | string | yes | – |
| ok | boolean | yes | – |
| usage | object | yes | – |
No examples provided.
runglance_list_work List RunGlance Work ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| 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.
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.
npm · @openly-useful/runglance-mcp
claude mcp add org-openlyuseful-runglance -- npx -y @openly-useful/runglance-mcp
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 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 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 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 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.
What did VerifyMCP test on the RunGlance MCP server?
VerifyMCP ran 16 checks on RunGlance, 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.