trigger_scan

3 registry entries were observed exposing a tool named trigger_scan — 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,346 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. io.github.bardesss/arr-mcpMCPcommunitytrust 60/100 · B
    v1.44.0
    ★ 68

    One server, 39 tools, the whole media stack: the *arrs, Jellyfin, Plex, Seerr and download clients

    io.github.bardesssUnknown3d agoGitHubobserved · static extraction
    mcp
  2. io.github.turbopress-de/turbometrics-mcpMCPcommunitylivetrust 60/100 · B
    v1.6.1

    Website performance monitoring: scans, Core Web Vitals, RUM data and alerts.

    ClaudeCursorCopilotChatGPTGemini
    io.github.turbopress-deUnknown4d agoGitHubobserved · static extraction
    mcp
  3. scannd-mcpMCPcommunitytrust 60/100 · B
    v0.1.0

    MCP server for Scannd (scannd.com) — trigger security scans and read reports/vulnerabilities from AI agents. Talks to the hosted Scannd REST API.

    ClaudeCursorCopilotGemini
    ScanndMIT2mo agonpmGitHubobserved · static extraction
    mcpmodel-context-protocolsecurityscannervulnerabilitynuclei

All indexed toolsSearch the registry for trigger_scan