Pituitary is a drift detection tool that ensures consistency in AI-native development by indexing documentation and specifications to catch discrepancies. It serves as a governance layer to prevent stale decisions and contradictions in project documentation.
From the registry: Catch spec drift before it catches you. Detect overlap, stale docs, and code drift.

$ brew install dusk-network/tap/pituitaryhttps://github.com/dusk-network/pituitary/releasesPlease install the `pituitary` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Pituitary binary** — Install via Homebrew (macOS) or download binary from GitHub Releases Run: `brew install dusk-network/tap/pituitary` (https://github.com/dusk-network/pituitary/releases)
Canonical MCP server config (stdio transport):
- command: `pituitary`
- args: ["serve","--config",".pituitary/pituitary.toml"]
Note: Consistency governance tool for specs and docs. No API keys required for core functionality. Optional: configure OpenAI-compatible embeddings for semantic retrieval. 13 tools. Run 'pituitary init --path .' first to index repository.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Validate oh-my-posh configurations and segment snippets against the official schema.
Real-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS.