statusline-kit vs QueueSim
statusline-kit is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
statusline-kit is a plugin bundle for AI coding tools published by Andrew Novykov. No marketplace we read lists it any more. QueueSim is an MCP server published by queuesim.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace endorphin-ai/hasbrains-agent-kit | Removed on 2026-10-24 Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | statusline-kitno longer listed · | QueueSim |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 9 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (queuesim.com/mcp/v1) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 5 | Not published |
| Parts of the bundle (differs) | 6 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/endorphin-ai/hasbrains-agent-kit | github.com/chiaha-ai/queuesim-site |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-17 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-22 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of statusline-kit
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Real-time status line showing context usage, costs, active tools, and session analytics.
-
Displays a rich, real-time status line at the bottom of your Claude Code session showing contextual information about the current conversation — including the active model, token…
-
Customizable status bar for Claude Code that displays real-time session metrics at the bottom of the terminal. Shows model name, thinking effort level, context usage with visual…
-
Local usage board for Claude Code. A hooks module records one metadata row per turn (exact engine cost, tokens by model, tool calls, agent spawns, context fill, rate-limit…
-
Experimental and utility skills: deployment, background tasks, pinning, summarization, skill testing, distillation, and context bootstrapping
-
Turnkey observability for AI coding agents - captures sessions and exports to Datadog LLM Observability
What each says it does
statusline-kit
Live status line and agent telemetry — the active /command or skill run with a timer, per-subagent context bar, model, estimated cost, tokens, duration and tool count, plus a per-run report. Run /statusline-kit:setup once to switch the status line on.
QueueSim
Run M/M/c queue simulations and four scenarios (call center, ER, coffee shop, single server).
How to run each
statusline-kit
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
QueueSim As a remote MCP server
claude mcp add --transport http public https://queuesim.com/mcp/v1Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only QueueSim has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: statusline-kit · What it can do: QueueSim · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.