Center Deep Core
A provider-backed preview for self-hosted metasearch and deterministic MCP evidence gathering. You choose the upstream providers, retention policy, and network boundary; it does not synthesize an LLM report.
# Clone and review the guided installer
git clone https://github.com/Unicorn-Commander/Center-Deep.git
cd Center-Deep
./install.sh
# Or start the repository's Compose stack
docker compose -f docker-compose.center-deep.yml up -dCompose starts the local stack; it does not provision identity, keys, Brigade, or every app.
Why Developers Choose Center Deep
A transparent preview for operators who want an inspectable search boundary.
Operator-Controlled Privacy
No advertising SDK is bundled. Local history may be retained, and upstream providers receive routed queries.
Configurable Providers
Normalize results from the upstream search providers and indexes you configure.
Observable Provider State
Readiness diagnostics and search responses make provider availability visible without exposing credentials.
Self-Hosted
Run on your infrastructure. Complete control over your search instance.
MCP Tools Built In
Tested search and deterministic deep_research tools return structured evidence without LLM synthesis.
Mobile Ready
A responsive interface supports desktop and small-screen search workflows.
Get Started with Docker
Choose your preferred installation method
🐳 Guided Installer
# Clone, review, and run the included installer
git clone https://github.com/Unicorn-Commander/Center-Deep.git
cd Center-Deep
./install.sh📦 Docker Compose
# From a cloned repository
docker compose -f docker-compose.center-deep.yml up -d
# View logs
docker compose -f docker-compose.center-deep.yml logs -f⚙️ Manual Installation
# Clone repository
git clone https://github.com/Unicorn-Commander/Center-Deep.git
cd Center-Deep
# Install dependencies
pip install -r requirements.txt
# Configure settings
cp .env.example .env
nano .env
# Run application
python app.pySystem Requirements
- Python 3.11+ or Docker
- Capacity sized for your traffic and chosen upstream provider
- Network access to the upstream provider endpoints you configure
- Redis connectivity is optional; the current search path does not cache provider responses
A Small, Inspectable Architecture
A Flask application dispatches structured requests to operator-configured providers.
Frontend
Server-rendered search UI
HTML5 • CSS3 • JavaScriptCore Engine
Provider dispatch and normalization
Python • Flask • Structured JSONSearch Providers
Operator-selected providers
SearXNG • Serper🔄 Deterministic Research
Multi-angle evidence gathering with normalized URLs and result de-duplication.
📋 Provider Readiness
Secret-free diagnostics report whether configured providers are ready.
🔌 Native MCP Surface
The tested MCP contract exposes search and deterministic deep-research tools.
🛡️ Deployment Boundary
Operators own credentials, TLS, provider access, retention, and network policy.
Explicit Configuration
Keep deployment choices in operator-controlled configuration.
Search Engines
Select supported upstream providers and configure their endpoints and required credentials.
Deployment Boundary
Set retention, authentication, session, provider, and network policy for your environment. Upstream provider policies still apply.
Interface Preferences
Browser theme and search preferences are UI controls; dashboard previews do not reconfigure containers or the active provider runtime.
Provider Reliability
Provider endpoints, credentials, and request timeouts live in deployment configuration.
Example Configuration
# Example provider configuration
CENTER_DEEP_SEARCH_PROVIDERS=searxng
SEARXNG_URL=http://searxng:8080
# Or add a configured Serper provider
# CENTER_DEEP_SEARCH_PROVIDERS=searxng,serper
# SERPER_API_KEY=replace-at-deployDiscovery for UC-1
An open search and evidence layer in the Unicorn Commander ecosystem.
Deep
Center Deep Core
AGPL-3.0 search and evidence substrate
Unicorn Commander
Complete command suite
Center Deep Core provides a provider-backed discovery boundary that UC-1 and other Magic Unicorn applications can call through MCP or REST interfaces.
Learn About UC-1 →Join the Community
Built by the community, for the community
Start Your Privacy Journey
Review the preview status, configure a reliable provider, and deploy on infrastructure you control
Book a call
An install, a product walkthrough, or a research conversation. Start with the right next step.
For humans and for agents
Bring your own agent.
Start with the connection details and the permissions for the product you want to use.
/.well-known/agent-card.json
Agent connection details are being prepared.