travis234-evidence-mcp

# Travis234 Evidence MCP `travis234-evidence-mcp` is the optional local evidence research engine for Travis234. It can find bounded source candidates, capture selected public pages, extract typed facts, retain disagreements, and answer with durable provenance. Discovery is convenient source selection; captured and queried page evidence is the factual record. ## What discovery does When a user asks a research question without links, the `discover` operation sends the bounded search query to the default hosted Exa MCP search service or an operator-selected Brave Search/public SearXNG route. It returns at most ten admitted candidates with opaque candidate IDs, URL, host, title, snippet, source hint, provider name, and deterministic rank. Every candidate is explicitly marked `verified=false`. Discovery removes common tracking parameters, checks each candidate URL with the same public-address policy used by acquisition, deduplicates equivalent results, and prefers a bounded mix of sources. It does not fetch every search result, crawl a domain, or turn a snippet into a claim. The model selects candidate IDs and passes them to `start`; only those selected pages enter the evidence pipeline. ## Discovery is not evidence Search titles, snippets, ranks, and source hints are unverified source-selection clues. They can help choose pages, but they cannot support a final factual answer. A qualified `query` row comes from a captured page and carries the source URL, capture time, SHA-256 content identity, and exact locator. Use this boundary in every answer: - candidate metadata explains why a source was selected; - `status` explains whether capture completed, was partial, failed, or was cancelled; - `query` supplies the source-qualified facts and conflicts used in chat; - `export` creates a durable report while returning receipt metadata only to Travis. This release does not qualify community sentiment or scholarly conclusions. Those need their own source policies, sampli…