Architecture-aware MCP context with boundaries, seams, impact scope, and BGI-TWIN guidance.
BGI is a static architecture analysis tool for large codebases. It groups code units by behavioral role and emits explicit architectural boundaries. Big Indexer is published in the MCP Registry as . Most architecture graphs fail at scale in two ways: giant clusters that collapse unrelated components together BGI is built to keep both under control, so the output remains usable on large repos. 1.…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
BGI is a static architecture analysis tool for large codebases. It groups code units by behavioral role and emits explicit architectural boundaries. Big Indexer is published in the MCP Registry as . Most architecture graphs fail at scale in two ways: giant clusters that collapse unrelated components together BGI is built to keep both under control, so the output remains usable on large repos. 1. "Where should this boundary be before we refactor?" BGI groups units by behavioral role (COV tokens…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.