mcpcost

org.openlyuseful/runglance

RunGlance

Is the RunGlance MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-27.

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

alive probed 2026-11-15 · unchanged since 2026-10-27

4tools
874tokens in Claude Opus 5.5
0.4 %of Claude's 200k window
0.3×the median server
248 msto initialize
14 msto list tools
Run it
npx -y @openly-useful/runglance-mcp@1.2.1 (stdio, probed in a container with the network off)
Host
npmjs.com
Reports itself as
runglance-mcp-server 1.2.1
Capabilities
resources, tools
Instructions
219 characters
Of a 1M window
<0.1 % of a 1M context window
Count
874 tokens in Claude Opus 5.5, exact, measured 2026-10-27. With the Claude Code prefix mcp__…__ on each tool name: 906. The o200k_base estimate is 483. Counted again when the tool definitions change. Method.
Repository
https://github.com/Openly-Useful/project-status
Registry
active, updated 2026-08-23 · registry entry
Changes
2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.81×.

Tool≈ Claude tokenso200k estimateShare of this server
runglance_list_work42723649 %
runglance_get_status1639019 %
runglance_get_usage1488217 %
runglance_get_locks1367516 %

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention progress or receipts.

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsClaudeo200k
2026-10-27 07:00alive264 ms4874483
2026-10-20 06:48alive248 ms4483

Badge for the README

mcpcost: alive

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher