Evaluation results are read in a dashboard and acted on in an editor, and the gap between those two places is where findings get lost. Putting the evals in the IDE is the whole point of this connection. The static key is the operational caveat — no consent flow, no expiry, so treat it like any other long-lived credential.
Galileo's endpoint for their LLM evaluation platform, which answered our handshake as EvalsInIDEServer 1.29.0. The name is the design intent: evaluation results where the code is, rather than in a separate dashboard.
Galileo's evaluation surface, reached from an MCP client. The endpoint requires the API key header before it will list what it exposes.
A Galileo-API-Key header with a static key. There is no OAuth.
Paste a URL with a key — add the endpoint to your client