hub_status

3 registry entries were observed exposing a tool named hub_status — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 13,585 of 49,880 scannable entries (27%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. @bzdos/hubdMCPcommunitytrust 60/100 · B
    v0.4.2
    ↓ 1k/wk

    Files-first project hub for mixed teams of AI agents and humans — shared journal, tasks, queues and a read-only kanban. MCP server + CLI, zero dependencies.

    ClaudeCursorCopilotGemini
    UnknownMIT3mo agonpmGitHubobserved · static extraction
    mcpagentsai-agentsclikanbanfiles-first
  2. @super-log/mcpMCPcommunitytrust 60/100 · B
    v0.4.1
    ↓ 8/wk
    ★ 1

    MCP server: let a coding agent query the super-log bench

    ClaudeCursorCopilotGemini
    Saxon Herschel NichollsMIT1mo agonpmGitHubobserved · static extraction
    mcploggingobservabilitysuper-logagentmodel-context-protocol
  3. com.super-log/super-log-cloudMCPcommunitylivetrust 60/100 · B
    v0.1.0
    ★ 1

    Read your team's hosted journal from an AI agent: every machine's streams, in hub order.

    ClaudeCursorCopilotChatGPTGemini
    com.super-logUnknown1mo agoGitHubobserved · static extraction
    mcp

All indexed toolsSearch the registry for hub_status