get_findings

6 registry entries were observed exposing a tool named get_findings — 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,491 of 26,663 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. @developerz.ai/ui-debugger-mcpverified
   trust 85/100 · AMCP serverobserved 2026-08-16 · static extraction
   Autonomous UI debugging MCP server: an agent drives the browser/desktop, reports bugs + UX issues.
2. @wcagc/mcp
   trust 60/100 · BMCP serverobserved 2026-08-16 · static extraction
   Deterministic axe-core accessibility scans (WCAG 2.1 AA, EN 301 549, PDF/UA) via your account.
3. @wphealthkit/mcp-server
   trust 60/100 · BMCP serverobserved 2026-08-17 · static extraction
   Security audits for WordPress plugins and themes — 62 verification layers, fix plans and SBOMs.
4. io.github.FinishKit/mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   FinishKit MCP: scan GitHub repos for security vulnerabilities, deployment blockers, and quality
5. io.github.PetriLahdelma/vertaaux-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Autonomous UX and a11y audit, fix, and verify loop. 38 tools, framework-aware patches.
6. 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.

All indexed toolsSearch the registry for get_findings