execute_scenario

2 registry entries were observed exposing a tool named execute_scenario — 1 of them as a privileged capability (a name matching exec / write / delete keywords).

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 10,040 of 31,325 scannable entries (32%) — 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. io.github.AishwaryShrivastav/vibe-testingMCPattestedtrust 85/100 · Aprivileged
    v0.4.2
    ★ 5

    Code-aware browser testing agent — 13 Playwright tools for AI code editors via MCP

    ClaudeCursorCopilotGemini
    io.github.AishwaryShrivastavUnknown3mo agonpmGitHubobserved · static extraction
    mcp
  2. vibe-testingMCPattestedtrust 65/100 · B
    v0.4.5
    ↓ 91/wk
    ★ 5

    Code-aware browser testing for AI coding agents. Reads your codebase so tests use real routes and field names, runs them in Playwright, remembers what broke, and reports what your last change fixed or regressed. No LLM calls inside. MCP server for Claude

    ClaudeCursorCopilotGemini
    Aishwary ShrivastavMIT1d agonpmGitHubobserved · static extraction
    testingbrowser-testingai-testingautomated-testingplaywrightmcp

All indexed toolsSearch the registry for execute_scenario