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 8,470 of 26,658 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.bardesss/arr-mcp
   trust 60/100 · BMCP serverobserved 2026-08-19 · static extraction
   One MCP server for the whole media stack: Radarr, Sonarr, Prowlarr, Bazarr, Jellyfin, Seerr
2. io.github.turbopress-de/turbometrics-mcp
   trust 60/100 · BMCP serverobserved 2026-06-14 · static extraction
   Website performance monitoring: scans, Core Web Vitals, RUM data and alerts.
3. scannd-mcp
   trust 60/100 · BMCP serverobserved 2026-08-15 · static extraction
   MCP server for Scannd (scannd.com) — trigger security scans and read reports/vulnerabilities from AI agents. Talks to the hosted Scannd REST

All indexed toolsSearch the registry for trigger_scan