Omni Scanner
Run 56+ automated codebase scanners from your agent before merge or release to catch git, architecture, and docs drift.
Overview
Omni Scanner is a MCP server for the Ship phase that runs 56+ scanners over your repo for git health, architecture, and documentation via MCP.
What is this MCP server?
- 56+ scanners covering git health, architecture, and documentation
- Codebase observatory model aimed at agent-driven audits
- PyPI package omni-governance version 0.7.3 with stdio MCP transport
- GitHub source at Pantheon-LadderWorks/omni-scanner
- Fits pre-merge and ongoing governance without replacing human review
- 56+ scanners per catalog description
- PyPI identifier omni-governance version 0.7.3
What problem does it solve?
You lack a single agent-callable pass that surfaces git, architecture, and docs problems before every release.
Who is it for?
Indie teams who want one MCP audit hub before PRs and during ongoing maintenance on growing codebases.
Skip if: Greenfield repos with almost no code, or teams that only need a single linter rule instead of a wide scanner suite.
What do I get? / Deliverables
After install, your agent can trigger a broad observatory scan and return actionable governance signals for review and iteration.
- Aggregated findings across 56+ git, architecture, and docs scanners
- Agent-friendly audit output for review and iteration backlogs
Recommended MCP Servers
Journey fit
Ship is the canonical shelf because the primary value is pre-release governance and review signals, even though you can re-run scans anytime. Review subphase matches architecture and documentation health checks that inform code review and release readiness.
How it compares
Multi-domain codebase observatory MCP, not a single-purpose ESLint plugin or production APM monitor.
Common Questions / FAQ
Who is Omni Scanner for?
Solo builders and small teams using coding agents who want consolidated git, architecture, and documentation scans from one MCP server.
When should I use Omni Scanner?
Use it in Ship before merge or release, and again in Operate when you need to track structural or docs drift on an established repo.
How do I add Omni Scanner to my agent?
Register the stdio MCP server using the omni-governance PyPI package from the Pantheon-LadderWorks omni-scanner repository in your agent MCP config.