analyze_file

5 registry entries were observed exposing a tool named analyze_file — none of them flagged as a privileged capability.

Spelled analyze_file, analyze-file in the wild — all one tool for the purposes of this page.

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.j0hanz/code-assistantverified
   trust 85/100 · AMCP serverobserved 2026-06-13 · static extraction
   Gemini-powered MCP server for code analysis.
2. io.github.j0hanz/code-lensverified
   trust 85/100 · AMCP serverobserved 2026-06-13 · static extraction
   Gemini-powered MCP server for code analysis.
3. tech-debt-mcp
   trust 60/100 · BMCP serverobserved 2026-08-09 · static extraction
   MCP Server for analyzing technical debt across multiple programming languages
4. io.github.mpzarde/fabric-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   MCP server for Fabric AI patterns
5. io.github.oabolade/figma_mcp_server_actor
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   MCP server enabling AI assistants to interact with Figma designs via natural language commands

All indexed toolsSearch the registry for analyze_file