Codebase observatory with 56+ scanners for git health, architecture, and documentation.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

The Federation Governance Tricorder β A modular, extensible observation engine that scans, maps, and guards codebases at galactic scale.
"Never trust documentation, trust reality." β ACE
Omni is a Python-powered passive observation platform that discovers the truth about your code. It doesn't modify files or break builds β it sees, maps, and reports. Think of it as a tricorder for your codebase: point it at any directory and it reveals structure, dependencies, health, drift, and compliance in seconds.
| Dimension | Reading |
|---|---|
| π Scanner Categories | 12 (from static analysis to git archaeology) |
| π¦ Total Scanners | 55 instruments across all categories |
| β‘ CLI Commands | 14 verbs for every observation need |
| π§ MCP Server | Exposes all scanners as AI-callable tools |
| ποΈ Pillars | 4 orchestration subsystems (Cartography, Intel, Gatekeeper, Registry) |
| π Federation Mode | Optional deep integration with a governance backend |
| 𦴠Standalone Mode | Works anywhere β no backend required |
New Here? Check out the Beginner's Guide: Zero to Hero for a step-by-step setup tutorial.
Omni follows the Trinity Architecture β three layers with strict separation of concerns:
Read-Only Guarantee: Scanners never modify source files. Only Builders write, and only to designated artifact directories.
For the full architectural deep-dive, see ARCHITECTURE.md.
Omni's 55 scanners are organized into 12 categories. Each scanner implements the universal scan(target: Path) β dict contract and is auto-discovered via SCANNER_MANIFEST.yaml files.
| Category | Scanners | Purpose |
|---|---|---|
| π static | 9 | Filesystem analysis β contracts, deps, docs, events, hooks, imports, surfaces, tools, UUIDs |
| ποΈ architecture | 4 | Structural enforcement β import boundaries, coupling detection, drift analysis, compliance |
| π discovery | 8 | Component cataloging β projects, CLI commands, cores, MCP servers, archives, census |
| π polyglot | 4 | Language ecosystems β Python packages, Node.js, Rust crates, generic (Go/Java/.NET/Docker) |
| π library | 6 | Document intelligence β cohesion analysis, content depth, knowledge graphs, rituals |
| π git | 5 | Repository intelligence β status, velocity, commit history, PR telemetry, utilities |
| π search | 3 | Pattern matching β file search, text search, regex pattern search with context |
| ποΈ db | 1 | Generic configuration-driven database scanning |
These scanners require the Federation Heart backend and are part of the proprietary governance layer. They appear in
omni introspectwhen the Heart is available but are not distributed with the open-source release.
| Category | Scanners | Purpose |
|---|---|---|
| π‘οΈ health | 6 | Runtime health β Federation, CMP, pillar, station, tunnel, and system status |
| ποΈ database | 5 | CMP entity scanning β agents, artifacts, conversations, entities, projects |
| β fleet | 1 | Fleet registry generation and validation |
| π₯ phoenix | 3 | Git history resurrection β archive scanning, orphan detection, temporal gap analysis |
Each category has its own README with detailed scanner documentation. See the Scanner Architecture Guide for the complete reference.
Pillars are orchestration subsystems that coordinate multiple scanners and produce higher-level intelligence:
| Pillar | Role | Key Capability |
|---|---|---|
| πΊοΈ Cartography | Ecosystem Mapper | Maps project constellations and dependency webs |
| π΅οΈ Intel | Intelligence Gatherer | Aggregates multi-scanner data into actionable insights |
| βοΈ Gatekeeper | Policy Enforcer | Validates compliance, catches drift, flags violations |
| π Registry | Registry Operator | Parses, validates, and manages PROJECT_REGISTRY_V1.yaml |
See Pillars Architecture for the deep dive.
| Command | Purpose |
|---|---|
omni scan | Run scanners against a target directory |
omni inspect | Deep inspection of a single project |
omni gate | Policy enforcement and compliance checks |
omni map | Ecosystem cartography and dependency mapping |
omni tree | Directory tree visualization |
omni audit | Provenance, dependency, and lock auditing |
omni registry | Registry operations and event scanning |
omni library | Grand Librarian document intelligence |
omni canon | Canon validation and discovery |
omni report | Generate structured reports |
omni init | Scaffold new Federation-compliant projects |
omni introspect | Self-inspection β shows all scanners, drift, capabilities |
omni interpret | Interpret and explain scan results |
omni inspect-tree | Combined tree + inspection |
Omni operates in two modes, transparently:
No external dependencies. Configuration from omni.yml and environment variables. All open-source scanners work perfectly. Ideal for individual developers and open-source projects.
When federation_heart is installed, Omni gains:
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/omni-scanner)<a href="https://allmcps.com/mcp/omni-scanner"><img src="https://allmcps.com/api/badge/omni-scanner?style=directory" alt="Omni Scanner on AllMCPs" /></a>