Documentation
¶
Overview ¶
Command context-server serves a directory of documents over MCP, so that Veritix's client mode has something to read.
It exists for three jobs and is honest about which is which. It is the instrument the aided half of dirty-meters' scorecard is measured with — `veritix eval testdata/dirty-meters` needs *something* serving `context/`, and the alternative was Veritix reading those files itself, which would have measured a feature that does not exist. It is how somebody evaluating Veritix points it at a folder of their own documentation without first writing an MCP server. And it is the smallest complete example of what a customer's own server has to do: list resources, read one by URI.
It is not part of the product and is not in the shipped binary. A real deployment connects to the customer's own dictionary, catalog or ticket system, which is theirs and already exists.
go run ./scripts/context-server -dir testdata/dirty-meters/context
./bin/veritix audit testdata/dirty-meters --llm anthropic \
--context-server "docs:go run ./scripts/context-server -dir testdata/dirty-meters/context"
Source Files