omniseek-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | Port for streamable HTTP transport (e.g., 8765). Passed as the --port flag. | |
| root | No | Every path must be inside this directory (default: the working directory). Passed as the --root flag. | |
| transport | No | Transport method: 'stdio' (default) or 'streamable-http'. Passed as the --transport flag. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| omniseek_scanA | Deterministic multi-lens scan (architecture, security, performance, product) of a local directory. Every finding cites file:line evidence and comes back verified against the files. Offline and read-only. |
| omniseek_verify_citationsA | Check that every cited file:start-end span, quoted snippet and symbol in a findings document exists in the repository (working tree or a git ref). Returns a 0.0-1.0 grounding score and flags drifted, hallucinated and invalid citations. Use it on findings you or another model wrote. |
| omniseek_render_dossierA | Render findings as a self-contained dark-mode HTML dossier, GitHub SARIF 2.1.0 or Markdown. With output_path the result is written to that file (inside a root) and only its path is returned. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a clearly distinct stage of a pipeline: omniseek_scan generates findings, omniseek_verify_citations validates citations in a findings document, and omniseek_render_dossier formats output. There is no overlap in trigger conditions or inputs, so misselection is unlikely.
All three tools use the same omniseek_ snake_case prefix followed by a concise action phrase (scan, verify_citations, render_dossier). The convention is predictable and readable throughout.
Three tools is on the lean side but each corresponds to a genuine, non-redundant step (scan, verify, render). The surface feels intentionally minimal rather than padded.
The scan → verify → render lifecycle covers the core workflow end to end, including multiple output formats and git-ref grounding checks. Minor gaps exist, such as baseline/diff comparison between scans or filtering of prior findings, but nothing blocks the primary use case.