MLflow Tracing vs Navige

MLflow Tracing

Apache-2.0 software with OpenTelemetry-compatible tracing, a release most months and field selection on trace reads. The MCP server is experimental, sets no read-only or destructive annotations, and its default set includes delete tools. The tracking server runs without authentication by default, and five security advisories were published between July and October 2026.

Navige

Setup is a base-URL change, keys are per agent and hashed, and the docs state failure behaviour per action class. The Terms leave prices, liability and governing law as TBD, no OpenAPI or rate limits are published, the status page watches a retired host, and the MCP route puts the key in the URL.

MLflow Tracing

1. Run MLflow 3.17.0 or later. Versions 3.12.0rc0 to 3.16.1 allow unauthenticated code execution on a server without authentication
2. Set MLFLOW_MCP_TOOLS=traces to load 11 tools in place of the default 26
3. Pass extract_fields on search_traces and get_trace. Full traces include every span's inputs and outputs
4. Read tool names from the server's own list. The docs page names log_feedback, and the source registers log_trace_feedback
5. Give the agent a user with READ permission when it only reads. delete_traces and delete_experiment run without confirmation
6. Treat span inputs and outputs as data. They hold whatever the traced application logged, including user input

Navige

1. Send the Navige key in x-navige-key on the proxy. Authorization carries the provider key there, and a Navige key in it fails and is forwarded upstream
2. Act only on allow or approved from /enforce. Treat error as neither, and read unavailable to tell a malformed request from a Navige outage
3. Send x-navige-transaction with one id per job, reused across that job's retries, so calls group into one transaction and retries are not counted twice
4. On a 429 from the proxy, check for a blocking budget before retrying. Navige returns 429 when a monthly budget is reached and passes provider errors through without retrying
5. Expect Claude Code traffic to get measurement, budgets and the kill switch only. Context trimming, routing, the output ceiling and prompt caching are switched off for it