get_pipeline_logs

2 registry entries were observed exposing a tool named get_pipeline_logs — 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 12,367 of 40,589 scannable entries (30%) — 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. @motiblog/mcpMCPcommunitylivetrust 60/100 · B
    v0.6.0
    ↓ 2k/wk

    Agent-first SEO research and publishing: competitors, SERPs, internal links, and Search Console

    ClaudeCursorCopilotChatGPTGemini
    UnknownUNLICENSED1mo agonpmGitHubobserved · static extraction
    mcpmodel-context-protocolblogseocontentagent
  2. @mushi-mushi/mcpMCPcommunitylivetrust 60/100 · B
    v0.24.6
    ↓ 183/wk
    ★ 3

    The bug mediator for AI-built apps: plain-English diagnosis + a ready fix, in your editor.

    ClaudeCursorCopilotChatGPTGemini
    io.github.kensaurusMIT3d agonpmGitHubobserved · static extraction
    mcp

All indexed toolsSearch the registry for get_pipeline_logs