diagnose_run

3 registry entries were observed exposing a tool named diagnose_run — 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,336 of 40,577 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. sparkforensics-mcpMCPcommunitytrust 60/100 · B
    v0.1.0
    ↓ 117/wk

    MCP server for diagnosing Apache Spark event-log performance issues and comparing runs.

    ClaudeCursorCopilotGemini
    io.github.shuffle-worksMIT1mo agonpmGitHubobserved · static extraction
    mcp
  2. devicecloud-mcpMCPcommunitytrust 60/100 · B
    v0.3.2
    ↓ 100/wk

    Triage failing DeviceCloud Maestro test runs from your AI assistant — fail reasons, failure screenshots, and flaky-flow analytics, without opening the web console

    ClaudeCursorCopilotGemini
    UnknownMIT2mo agonpmGitHubobserved · static extraction
    mcpmodel-context-protocoldevicecloudmaestrotestingmobile
  3. @intencion/mcpMCPcommunitytrust 60/100 · B
    v0.1.1

    MCP server for debugging AI-agent runs from your editor with Intencion. Lets Claude Code and Cursor explain why an agent run failed, with evidence.

    ClaudeCursorCopilotGemini
    IntencionMIT3mo agonpmGitHubobserved · static extraction
    mcpmodel-context-protocolaiagentsagent-debuggingobservability

All indexed toolsSearch the registry for diagnose_run