report_outcome

6 registry entries were observed exposing a tool named report_outcome — 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. @debugai/mcp
   trust 60/100 · BMCP serverobserved 2026-08-17 · static extraction
   MCP server for DebugAI. Browser sign-in, auto client setup, no key pasting.
2. @kansei-link/mcp-server
   trust 60/100 · BMCP serverobserved 2026-08-13 · static extraction
   SaaS intelligence for AI agents. 5 unified tools cover 1,000+ services with 91-96% token savings.
3. @usekaval/mcp
   trust 60/100 · BMCP serverobserved 2026-07-21 · static extraction
   Verify the facts an agent's action depends on before it acts — ALLOW, REVIEW, or BLOCK.
4. io.github.ArcedeDev/air-sdk
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Collective intelligence for browser automation agents. Site capabilities, selectors, and extraction.
5. io.github.kaditang/402sentinel-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   x402 payment safety for AI agents: counterparty risk gate, payment firewall, compliance, RWA gate.
6. io.github.meltingpixelsai/zero-core-verify
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Post-tx outcome verification via LLM-as-judge. Zero Core Verify.

All indexed toolsSearch the registry for report_outcome