analyze_codebase

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

Spelled analyze_codebase, analyze-codebase 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,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. @skillsmith/mcp-serververified
   trust 85/100 · AMCP serverobserved 2026-08-14 · static extraction
   Publish versioned agent skills to a team-scoped registry, track drift, and deprecate stale ones.
2. io.github.maroondlabs/sourcebook
   trust 60/100 · BMCP serverobserved 2026-06-14 · static extraction
   Live codebase intelligence for AI agents: conventions, blast radius, import graphs, git insights.
3. io.github.nirholas/repo-intel
   trust 60/100 · BMCP serverobserved 2026-06-14 · static extraction
   Analyze repos of any size - security scanning code analysis monorepo support
4. io.github.pi22by7/in-memoria
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Persistent codebase intelligence that gives AI assistants memory across sessions
5. io.github.Vrun-design/openflowkit-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Local-first OpenFlowKit diagramming tools for Claude, Cursor, Windsurf & other MCP clients.

All indexed toolsSearch the registry for analyze_codebase