get_trace

6 registry entries were observed exposing a tool named get_trace — 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. trust 85/100 · AMCP serverobserved · static extraction
    Query Spanlens LLM observability from Cursor, Claude Desktop, or Continue via MCP.
  2. trust 60/100 · BMCP serverobserved · static extraction
    MCP server for debugging AI-agent runs from your editor with Intencion. Lets Claude Code and Cursor explain why an agent run failed, with ev
  3. trust 60/100 · BMCP serverobserved · static extraction
    Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.
  4. trust 60/100 · BMCP serverobserved · static extraction
    AI prompt optimization for 58+ platforms across 7 categories with custom platforms
  5. trust 60/100 · BMCP serverobserved · static extraction
    Structured execution trace and span logging for AI agents
  6. trust 60/100 · BMCP serverobserved · static extraction
    Provable, declarative multi-agent workflows for Claude Code (typed .slang, non-LLM executor).

All indexed toolsSearch the registry for get_trace