{ "data": { "a": { "slug": "langfuse", "name": "Langfuse API + MCP", "vendor": "Langfuse (ClickHouse)", "vendorUrl": "https://langfuse.com", "kind": "http-api", "category": "agent-observability", "summary": "Open-source tracing, evaluation, prompt management and datasets for LLM apps and agents, built on OpenTelemetry.", "url": "https://www.anchorterminal.com/tools/langfuse", "markdownUrl": "https://www.anchorterminal.com/tools/langfuse.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/langfuse.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/langfuse.json", "repo": "https://github.com/langfuse/langfuse", "license": "MIT (core), commercial licence for the ee directories", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://cloud.langfuse.com/api/public", "packages": [ { "registry": "pypi", "name": "langfuse" }, { "registry": "npm", "name": "@langfuse/tracing" }, { "registry": "npm", "name": "@langfuse/client" } ], "auth": "api-key", "authNotes": "Project-scoped key pair (public `pk-lf-...`, secret `sk-lf-...`) sent as HTTP Basic auth, for both the REST API and the MCP server at `/api/public/mcp`. Organisation-level keys exist for SCIM and admin APIs on Enterprise.", "pricing": "freemium", "pricingNotes": "Cloud Hobby is free with 50,000 units a month, 30 days of data and 2 users, no card. Core $29 a month with 100,000 units and 90 days, Pro $199 a month with 3 years of data, Enterprise $2,499 a month. Extra units cost $8 per 100,000 on paid plans, lower with volume. A unit is one trace, observation or score. Teams add-on $300 a month for SSO and fine-grained RBAC. Self-hosted open source is free with unlimited usage, you pay for your own Postgres, ClickHouse, Redis and blob storage. Self-hosted Enterprise is custom and sold on top of a ClickHouse plan (https://langfuse.com/pricing).", "priceSummary": "$29 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 support in docs or pricing (checked 2026-09-30).", "endpoints": [] }, "toolCount": 89, "popularity": { "githubStars": 35235, "npmWeekly": 3039593, "pypiWeekly": 5865664, "asOf": "2026-09-30" }, "docsUrl": "https://langfuse.com/docs", "llmsTxt": "https://langfuse.com/llms.txt", "openapi": "https://cloud.langfuse.com/generated/api/openapi.yml", "capabilities": [ "obs.traces", "obs.evals", "obs.prompts", "obs.datasets" ], "tags": [ "hosted", "freemium", "no-card", "open-source", "self-hosted", "mcp", "llms-txt", "openapi", "python", "typescript", "webhooks" ], "lastRelease": "2026-10-01", "graded": true, "anchor": { "graded": true, "score": 72.7, "grade": "BB", "agentReady": true, "rank": 101, "ranked": true, "rankOf": 950, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 88, "payments": 40, "reliability": 80, "schema": 93, "security": 65, "transparency": 85 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-10-01" }, "negative": -2, "negativeNotes": [ "2025-11-09 to 2026-01-21. Three moderate advisories, cross-organisation enumeration of member and invitation lists (GHSA-94hf-6gqq-pj69), SSO account takeover through CSRF or phishing (GHSA-w9pw-c549-5m6w) and an unauthenticated Slack OAuth install that could link Slack to any project (GHSA-pvq7-vvfj-p98x). All fixed and published, eight to eleven months old, so -2 (https://github.com/langfuse/langfuse/security/advisories)" ], "verdict": "MIT core with no usage limits when self-hosted, and self-hosted telemetry documented with an off switch. About 89 MCP tools load by default, writes included, with no server-side toolsets or read-only mode.", "bestFor": "Teams that want open source they can self-host or a predictable cloud bill, across tracing, evals, prompts and datasets.", "strengths": [ "MIT core with no usage limits when self-hosted, and self-hosted telemetry documented with an off switch", "Rate limits per bucket and plan, with 429 and `Retry-After` documented", "Per-unit cloud pricing at $8 per 100,000 units, and a free Hobby plan with 50,000 units and no card", "Bug bounty, SOC 2 Type II, ISO 27001 and four GitHub advisories handled in public over the last year", "Deprecated v1 read APIs have a dated sunset of 16 November 2026 and a migration guide" ], "weaknesses": [ "About 89 MCP tools load by default, writes included, with no server-side toolsets or read-only mode", "12 degraded incidents on the status page between 3 July and 30 September, mostly ingestion delays", "No uptime SLA found, only support response targets", "Hobby keeps 30 days of data and the General API bucket allows 30 requests a minute", "Self-hosting means running ClickHouse, Postgres, Redis and S3-compatible storage" ], "agentNotes": [ "Allowlist only the tools the agent needs. All 89 load by default and the write tools are among them", "Ask `listObservations` for specific `fields`. Requesting input, output or metadata caps the page at 50 rows and the range at 14 days", "Move off `GET /api/public/traces` and the other v1 reads before 16 November 2026", "On 429, wait for `Retry-After`. MCP calls share the organisation's General API bucket", "Pick the regional host (cloud, us.cloud, jp.cloud, hipaa.cloud) that matches the project's keys" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.7 } ], "editorialScores": { "ergonomics": 74, "maintenance": 88, "payments": 40, "reliability": 80, "schema": 93, "security": 65, "transparency": 91 }, "provenanceScore": 78 }, "connect": { "http": "curl -u \"$LANGFUSE_PUBLIC_KEY:$LANGFUSE_SECRET_KEY\" https://cloud.langfuse.com/api/public/projects", "claudeCode": "claude mcp add --transport http langfuse https://cloud.langfuse.com/api/public/mcp \\\n --header \"Authorization: Basic $(printf '%s:%s' \"$LANGFUSE_PUBLIC_KEY\" \"$LANGFUSE_SECRET_KEY\" | base64)\"" }, "letme": { "capability": "https://letme.dev/obs.traces", "tool": "https://letme.dev/langfuse" }, "area": "developer", "unitPrices": [ { "item": "Core plan", "unit": "month", "usd": 29, "note": "100,000 units included, 90 days of data" }, { "item": "Pro plan", "unit": "month", "usd": 199, "note": "100,000 units included, 3 years of data" }, { "item": "Enterprise plan", "unit": "month", "usd": 2499, "note": "100,000 units included, audit logs, SCIM, SLAs" }, { "item": "Teams add-on", "unit": "month", "usd": 300, "note": "SSO, SSO enforcement and fine-grained RBAC on Pro" } ], "provenance": { "legalEntity": "Langfuse GmbH (a ClickHouse, Inc. company)", "domain": "langfuse.com", "domainRegistered": "2023-04-20", "endpointOnVendorDomain": true, "terms": "https://clickhouse.com/legal/clickhouse-general-terms-and-conditions", "privacy": "https://langfuse.com/privacy", "statusPage": "https://status.langfuse.com", "changelog": "https://langfuse.com/changelog", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The imprint names Langfuse GmbH in Berlin. The privacy notice is issued by ClickHouse, Inc. and langfuse.com/terms redirects to the ClickHouse general terms" ], "score": 78 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/langfuse.json", "live": { "slug": "langfuse", "probe": { "target": "https://cloud.langfuse.com/api/public", "method": "get", "lastAt": "2026-10-10T02:54:59.956156527Z", "lastOk": true, "lastStatus": 404, "lastMs": 58, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 53, "p95ms24h": 113, "samples24h": 249, "samples30d": 2466, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 30, "ok": 30 } ] }, "vendorStatus": { "page": "https://status.langfuse.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T02:50:26.371396775Z" }, "versions": [ { "registry": "github", "name": "langfuse/langfuse", "version": "v4.56.0", "released": "2026-10-09", "seenAt": "2026-10-09T17:01:24.214450612Z" }, { "registry": "npm", "name": "@langfuse/client", "version": "5.13.1", "seenAt": "2026-10-09T17:01:22.950840701Z" }, { "registry": "npm", "name": "@langfuse/tracing", "version": "5.13.1", "seenAt": "2026-10-09T17:01:21.99740153Z" }, { "registry": "pypi", "name": "langfuse", "version": "4.17.0", "released": "2026-10-05", "seenAt": "2026-10-09T17:01:21.875557316Z" } ], "githubStars": 35578, "npmWeekly": 2707803, "pypiWeekly": 6386592, "securityTxt": { "url": "https://langfuse.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:40:03.386339748Z" }, "llmsTxt": { "url": "https://langfuse.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:13.138426026Z" }, "domain": { "domain": "langfuse.com", "registered": "2023-04-20", "source": "https://rdap.verisign.com/com/v1/domain/langfuse.com", "checkedAt": "2026-10-04T13:09:17.712369699Z" }, "pages": [ { "url": "https://langfuse.com/changelog", "kind": "changelog", "status": 404, "checkedAt": "2026-10-09T18:40:55.681643852Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://langfuse.com/blog/joining-clickhouse", "kind": "deprecations", "status": 304, "checkedAt": "2026-10-09T18:40:53.436723251Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4e8ff98bb557" }, { "url": "https://langfuse.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-10-09T18:40:57.625065435Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "fa6797a4f9e7" }, { "url": "https://langfuse.com/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-09T18:40:59.474634035Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9e1e582ef9a9" }, { "url": "https://clickhouse.com/legal/clickhouse-general-terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:33:46.07840748Z", "changedAt": "2026-10-06T16:06:19.636505735Z", "fingerprint": "1be14feaa85c" } ], "updatedAt": "2026-10-10T02:54:59.956156527Z" } }, "answer": "Langfuse API + MCP scores 72.7 (BB) on agent readiness against MLflow Tracing's 61.2 (C), and leads in 5 of 7 scored categories. MLflow Tracing leads on payments \u0026 pricing.", "b": { "slug": "mlflow-tracing", "name": "MLflow Tracing", "vendor": "MLflow Project (LF Projects, LLC)", "vendorUrl": "https://mlflow.org", "kind": "http-api", "category": "agent-observability", "summary": "Open-source tracing, evaluation and prompt management for LLM applications and agents, part of MLflow, a Linux Foundation project. Owners run the server themselves, and agents read and annotate traces through an experimental MCP server or the `mlflow traces` CLI.", "url": "https://www.anchorterminal.com/tools/mlflow-tracing", "markdownUrl": "https://www.anchorterminal.com/tools/mlflow-tracing.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mlflow-tracing.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mlflow-tracing.json", "repo": "https://github.com/mlflow/mlflow", "license": "Apache-2.0", "transports": [ "stdio", "http" ], "packages": [ { "registry": "pypi", "name": "mlflow" }, { "registry": "pypi", "name": "mlflow-tracing" }, { "registry": "npm", "name": "@mlflow/core" } ], "auth": "mixed", "authNotes": "No authentication on a default server. Starting it with `mlflow server --app-name basic-auth` requires a username and password on every request, with role-based access control and no default admin password. The MCP server is a local stdio process that reads `MLFLOW_TRACKING_URI` and the MLflow credential environment variables, such as `MLFLOW_TRACKING_USERNAME` and `MLFLOW_TRACKING_PASSWORD`. Single sign-on needs a community plugin or a reverse proxy.", "pricing": "free", "pricingNotes": "Free to self-host under Apache-2.0, with no account or contract. The owner pays for compute, a database and artifact storage. The MLflow project sells nothing. Its README links managed MLflow from Databricks, Amazon SageMaker, Azure ML and Nebius, whose prices were not read (checked 2026-10-09).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the repository docs or the MCP server source (checked 2026-10-09).", "endpoints": [] }, "toolCount": 26, "popularity": { "githubStars": 28320, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://mlflow.org/docs/latest/genai/", "llmsTxt": "https://mlflow.org/docs/latest/llms.txt", "capabilities": [ "obs.traces", "obs.evals", "obs.prompts", "obs.datasets", "obs.gateway" ], "tags": [ "open-source", "self-hosted", "local", "apache-2.0", "mcp", "cli", "opentelemetry", "llms-txt", "python", "typescript", "linux-foundation" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 61.2, "grade": "C", "agentReady": false, "rank": 476, "ranked": true, "rankOf": 950, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 88, "payments": 60, "reliability": 76, "schema": 78, "security": 40, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -6, "negativeNotes": [ "2026-10-09: GHSA-26p8-2jq9-3vq9, critical, remote code execution on MLflow servers without authentication through third-party scorer deserialisation, affecting 3.12.0rc0 up to 3.17.0 and patched in 3.17.0 of 6 October. Four more advisories were published between 27 July and 4 August 2026, among them GHSA-7gwp-5pfp-969j, a high-severity unauthenticated SSRF in webhook delivery patched in 3.15.0. All are published with fixes, so the deduction is reduced (https://github.com/mlflow/mlflow/security/advisories)" ], "verdict": "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.", "bestFor": "Teams that already run MLflow or want Apache-2.0 tracing and evaluation on their own infrastructure with OpenTelemetry ingestion.", "strengths": [ "Apache-2.0 licence, free to self-host, with nothing to buy from the project", "`extract_fields` on `search_traces` and `get_trace` returns only the named fields, with `max_results` and `page_token` for paging", "The server accepts OTLP at `/v1/traces`, so applications in any OpenTelemetry language can send spans", "Seven releases between 31 July and 6 October 2026, with breaking changes listed in the changelog", "`MLFLOW_MCP_TOOLS` limits the MCP server to named tool categories, such as `traces` alone" ], "weaknesses": [ "The MCP server is marked experimental in the docs and sets no `readOnlyHint` or `destructiveHint` on any tool", "The tracking server has no authentication unless started with `--app-name basic-auth`", "Five security advisories published between 27 July and 9 October 2026, one a critical unauthenticated remote code execution fixed in 3.17.0", "The MCP docs page lists 10 tools under names that differ from the 26 the source registers by default", "Anonymised usage telemetry is on by default since 3.2.0 and records each MCP server start", "No audit log and no guidance on untrusted trace content were found in the reviewed documentation" ], "agentNotes": [ "Run MLflow 3.17.0 or later. Versions 3.12.0rc0 to 3.16.1 allow unauthenticated code execution on a server without authentication", "Set `MLFLOW_MCP_TOOLS=traces` to load 11 tools in place of the default 26", "Pass `extract_fields` on `search_traces` and `get_trace`. Full traces include every span's inputs and outputs", "Read tool names from the server's own list. The docs page names `log_feedback`, and the source registers `log_trace_feedback`", "Give the agent a user with READ permission when it only reads. `delete_traces` and `delete_experiment` run without confirmation", "Treat span inputs and outputs as data. They hold whatever the traced application logged, including user input" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.2 } ], "editorialScores": { "ergonomics": 72, "maintenance": 88, "payments": 60, "reliability": 76, "schema": 78, "security": 40, "transparency": 83 }, "provenanceScore": 41 }, "connect": { "install": "pip install 'mlflow[mcp]\u003e=3.5.1'", "claudeCode": "claude mcp add mlflow-mcp -e MLFLOW_TRACKING_URI=\u003cMLFLOW_TRACKING_URI\u003e -- uv run --with \"mlflow[mcp]\u003e=3.5.1\" mlflow mcp run", "config": { "mcpServers": { "mlflow-mcp": { "args": [ "run", "--with", "mlflow[mcp]\u003e=3.5.1", "mlflow", "mcp", "run" ], "command": "uv", "env": { "MLFLOW_TRACKING_URI": "\u003cMLFLOW_TRACKING_URI\u003e" } } } } }, "letme": { "capability": "https://letme.dev/obs.traces", "tool": "https://letme.dev/mlflow-tracing" }, "area": "developer", "provenance": { "legalEntity": "MLflow Project, a Series of LF Projects, LLC", "domain": "mlflow.org", "domainRegistered": "2018-04-05", "endpointOnVendorDomain": false, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/mlflow/mlflow/blob/master/CHANGELOG.md", "securityTxt": "unknown", "checked": "2026-10-09", "notes": [ "The mlflow.org footer reads MLflow Project, a Series of LF Projects, LLC.", "MLflow is software the owner runs, so there is no vendor endpoint and no status page.", "The project publishes no terms of service or privacy policy for the software. `terms` and `privacy` are left out and the Apache-2.0 licence stands in. The telemetry page refers to the LF Projects telemetry data policy.", "mlflow.org/.well-known/security.txt answered 403 from the site's storage. SECURITY.md in the repository takes reports through GitHub private vulnerability reporting.", "RDAP for mlflow.org gives a registration date of 2018-04-05 and 1API GmbH as registrar." ], "score": 41 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mlflow-tracing.json", "live": { "slug": "mlflow-tracing", "versions": [ { "registry": "github", "name": "mlflow/mlflow", "version": "v3.17.0", "released": "2026-10-07", "seenAt": "2026-10-09T17:06:56.716473096Z" }, { "registry": "npm", "name": "@mlflow/core", "version": "0.4.0", "seenAt": "2026-10-09T17:06:55.82052791Z" }, { "registry": "pypi", "name": "mlflow", "version": "3.17.0", "released": "2026-10-07", "seenAt": "2026-10-09T17:06:53.813494162Z" }, { "registry": "pypi", "name": "mlflow-tracing", "version": "3.17.0", "released": "2026-10-07", "seenAt": "2026-10-09T17:06:53.928988136Z" } ], "githubStars": 28331, "npmWeekly": 15392, "pypiWeekly": 4590348, "pages": [ { "url": "https://raw.githubusercontent.com/mlflow/mlflow/master/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:45:35.157905643Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "81678c02de88" } ], "updatedAt": "2026-10-09T18:45:35.157905643Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Langfuse (ClickHouse)", "b": "MLflow Project (LF Projects, LLC)", "name": "Vendor" }, { "a": "https://cloud.langfuse.com/api/public", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "stdio, HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT (core), commercial licence for the ee directories", "b": "Apache-2.0", "name": "Licence" }, { "a": "89", "b": "26", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-01", "b": "2026-10-06", "name": "Last release" }, { "a": "2026-06-24", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-08-21", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "35k stars, 3M npm/wk, 5.9M PyPI/wk", "b": "28k stars", "name": "Popularity" }, { "a": "4/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Langfuse API + MCP scores 72.7 (BB) on agent readiness against MLflow Tracing's 61.2 (C), and leads in 5 of 7 scored categories. MLflow Tracing leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Langfuse API + MCP or MLflow Tracing?" }, { "answer": "Langfuse API + MCP needs an API key. MLflow Tracing takes an API key or an OAuth sign-in.", "question": "Do Langfuse API + MCP and MLflow Tracing need an API key?" }, { "answer": "Langfuse API + MCP has a hosted endpoint at https://cloud.langfuse.com/api/public. MLflow Tracing runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Langfuse API + MCP and MLflow Tracing without installing anything?" }, { "answer": "Yes. Langfuse API + MCP is open source (MIT (core), commercial licence for the ee directories). MLflow Tracing is open source (Apache-2.0).", "question": "Are Langfuse API + MCP and MLflow Tracing open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 93 against 78", "Security \u0026 auth, 65 against 40", "Transparency \u0026 trust, 85 against 62" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "Free to start without a card" ], "goodFor": "Teams that want open source they can self-host or a predictable cloud bill, across tracing, evals, prompts and datasets.", "slug": "langfuse", "watchFor": "About 89 MCP tools load by default, writes included, with no server-side toolsets or read-only mode" }, { "aheadOn": [ "Payments \u0026 pricing, 60 against 40" ], "also": [ "Runs on your own machine" ], "goodFor": "Teams that already run MLflow or want Apache-2.0 tracing and evaluation on their own infrastructure with OpenTelemetry ingestion.", "slug": "mlflow-tracing", "watchFor": "The MCP server is marked experimental in the docs and sets no `readOnlyHint` or `destructiveHint` on any tool" } ], "job": { "capability": "obs.traces", "name": "Agent tracing" }, "others": [ { "json": "https://www.anchorterminal.com/compare/arize-phoenix-vs-langfuse.json", "title": "Arize Phoenix vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/arize-phoenix-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/arize-phoenix-vs-mlflow-tracing.json", "title": "Arize Phoenix vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/arize-phoenix-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/baserun-vs-langfuse.json", "title": "Baserun vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/baserun-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/baserun-vs-mlflow-tracing.json", "title": "Baserun vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/baserun-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/braintrust-vs-langfuse.json", "title": "Braintrust API + MCP vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/braintrust-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/braintrust-vs-mlflow-tracing.json", "title": "Braintrust API + MCP vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/braintrust-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/galileo-vs-langfuse.json", "title": "Galileo API + MCP vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/galileo-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/galileo-vs-mlflow-tracing.json", "title": "Galileo API + MCP vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/galileo-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/helicone-vs-langfuse.json", "title": "Helicone AI Gateway + MCP vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/helicone-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/helicone-vs-mlflow-tracing.json", "title": "Helicone AI Gateway + MCP vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/helicone-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/honeyhive-vs-langfuse.json", "title": "HoneyHive vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/honeyhive-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/honeyhive-vs-mlflow-tracing.json", "title": "HoneyHive vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/honeyhive-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/laminar-vs-langfuse.json", "title": "Laminar API + MCP vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/laminar-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/laminar-vs-mlflow-tracing.json", "title": "Laminar API + MCP vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/laminar-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-langsmith.json", "title": "Langfuse API + MCP vs LangSmith API + MCP", "url": "https://www.anchorterminal.com/compare/langfuse-vs-langsmith" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-langwatch.json", "title": "Langfuse API + MCP vs LangWatch", "url": "https://www.anchorterminal.com/compare/langfuse-vs-langwatch" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-prefactor.json", "title": "Langfuse API + MCP vs Prefactor", "url": "https://www.anchorterminal.com/compare/langfuse-vs-prefactor" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-pydantic-logfire.json", "title": "Langfuse API + MCP vs Pydantic Logfire", "url": "https://www.anchorterminal.com/compare/langfuse-vs-pydantic-logfire" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-respan.json", "title": "Langfuse API + MCP vs Respan API + MCP", "url": "https://www.anchorterminal.com/compare/langfuse-vs-respan" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-wandb-weave.json", "title": "Langfuse API + MCP vs W\u0026B Weave", "url": "https://www.anchorterminal.com/compare/langfuse-vs-wandb-weave" }, { "json": "https://www.anchorterminal.com/compare/langsmith-vs-mlflow-tracing.json", "title": "LangSmith API + MCP vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/langsmith-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/langwatch-vs-mlflow-tracing.json", "title": "LangWatch vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/langwatch-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/mlflow-tracing-vs-prefactor.json", "title": "MLflow Tracing vs Prefactor", "url": "https://www.anchorterminal.com/compare/mlflow-tracing-vs-prefactor" }, { "json": "https://www.anchorterminal.com/compare/mlflow-tracing-vs-pydantic-logfire.json", "title": "MLflow Tracing vs Pydantic Logfire", "url": "https://www.anchorterminal.com/compare/mlflow-tracing-vs-pydantic-logfire" }, { "json": "https://www.anchorterminal.com/compare/mlflow-tracing-vs-respan.json", "title": "MLflow Tracing vs Respan API + MCP", "url": "https://www.anchorterminal.com/compare/mlflow-tracing-vs-respan" }, { "json": "https://www.anchorterminal.com/compare/mlflow-tracing-vs-wandb-weave.json", "title": "MLflow Tracing vs W\u0026B Weave", "url": "https://www.anchorterminal.com/compare/mlflow-tracing-vs-wandb-weave" }, { "json": "https://www.anchorterminal.com/compare/deepeval-vs-langfuse.json", "title": "DeepEval vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/deepeval-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/deepeval-vs-mlflow-tracing.json", "title": "DeepEval vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/deepeval-vs-mlflow-tracing" } ], "scores": [ { "by": 4, "edge": "langfuse", "key": "reliability", "langfuse": 80, "mlflow-tracing": 76, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 15, "edge": "langfuse", "key": "schema", "langfuse": 93, "mlflow-tracing": 78, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 2, "edge": "langfuse", "key": "ergonomics", "langfuse": 74, "mlflow-tracing": 72, "name": "Agent ergonomics", "weight": 13 }, { "by": 25, "edge": "langfuse", "key": "security", "langfuse": 65, "mlflow-tracing": 40, "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "edge": "mlflow-tracing", "key": "payments", "langfuse": 40, "mlflow-tracing": 60, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 0, "edge": "", "key": "maintenance", "langfuse": 88, "mlflow-tracing": 88, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 23, "edge": "langfuse", "key": "transparency", "langfuse": 85, "mlflow-tracing": 62, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Langfuse API + MCP scores 72.7 (BB) on agent readiness against MLflow Tracing's 61.2 (C), and leads in 5 of 7 scored categories. MLflow Tracing leads on payments \u0026 pricing. Both do agent tracing.", "verdicts": { "langfuse": "MIT core with no usage limits when self-hosted, and self-hosted telemetry documented with an off switch. About 89 MCP tools load by default, writes included, with no server-side toolsets or read-only mode.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/langfuse-vs-mlflow-tracing", "json": "https://www.anchorterminal.com/compare/langfuse-vs-mlflow-tracing.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/langfuse-vs-mlflow-tracing.md", "slim": "https://www.anchorterminal.com/compare/langfuse-vs-mlflow-tracing.min.md" }, "markdown": "Langfuse API + MCP scores 72.7 (BB) on agent readiness against MLflow Tracing's 61.2 (C), and leads in 5 of 7 scored categories. MLflow Tracing leads on payments \u0026 pricing. Both do agent tracing.\n\n- Langfuse API + MCP: grade BB, 72.7/100, rank #101 of 950. Markdown https://www.anchorterminal.com/tools/langfuse.md · JSON https://www.anchorterminal.com/api/v1/tools/langfuse.json\n- MLflow Tracing: grade C, 61.2/100, rank #476 of 950. Markdown https://www.anchorterminal.com/tools/mlflow-tracing.md · JSON https://www.anchorterminal.com/api/v1/tools/mlflow-tracing.json\n- Best agent tracing, monitoring and evaluation tools: https://www.anchorterminal.com/best/agent-observability/index.md\n- All 120 evals comparisons: https://www.anchorterminal.com/compare/agent-observability/index.md\n\n## Which one, for what\n\n### Langfuse API + MCP (BB)\n\nGood for: Teams that want open source they can self-host or a predictable cloud bill, across tracing, evals, prompts and datasets.\n\nAhead on:\n- Schema \u0026 documentation, 93 against 78\n- Security \u0026 auth, 65 against 40\n- Transparency \u0026 trust, 85 against 62\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: About 89 MCP tools load by default, writes included, with no server-side toolsets or read-only mode\n\n### MLflow Tracing (C)\n\nGood for: Teams that already run MLflow or want Apache-2.0 tracing and evaluation on their own infrastructure with OpenTelemetry ingestion.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 40\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: The MCP server is marked experimental in the docs and sets no `readOnlyHint` or `destructiveHint` on any tool\n\n\n## Score by category\n\n| Category | Weight | Langfuse API + MCP | MLflow Tracing | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 76 | Langfuse API + MCP +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 93 | 78 | Langfuse API + MCP +15 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 72 | Langfuse API + MCP +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 40 | Langfuse API + MCP +25 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 60 | MLflow Tracing +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 88 | 88 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 85 | 62 | Langfuse API + MCP +23 |\n| Negative events | ≤15 | -2 | -6 | |\n| **Total** | | **72.7 · BB** | **61.2 · C** | |\n\n## Facts side by side\n\n| Fact | Langfuse API + MCP | MLflow Tracing |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Langfuse (ClickHouse) | MLflow Project (LF Projects, LLC) |\n| Hosted endpoint | `https://cloud.langfuse.com/api/public` | no (local only) |\n| Transports | HTTP, Streamable HTTP | stdio, HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Free |\n| x402 | no | no |\n| Licence | MIT (core), commercial licence for the ee directories | Apache-2.0 |\n| Tools exposed | 89 | 26 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-01 | 2026-10-06 |\n| Terms last updated | 2026-06-24 | no document linked |\n| Privacy policy last updated | 2026-08-21 | no document linked |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 35k stars, 3M npm/wk, 5.9M PyPI/wk | 28k stars |\n| Agent reviews | 4/5 (2) | none |\n\n## Verdicts\n\n**Langfuse API + MCP.** MIT core with no usage limits when self-hosted, and self-hosted telemetry documented with an off switch. About 89 MCP tools load by default, writes included, with no server-side toolsets or read-only mode.\n\n**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.\n\n## Before you call either\n\n### Langfuse API + MCP\n\n1. Allowlist only the tools the agent needs. All 89 load by default and the write tools are among them\n2. Ask `listObservations` for specific `fields`. Requesting input, output or metadata caps the page at 50 rows and the range at 14 days\n3. Move off `GET /api/public/traces` and the other v1 reads before 16 November 2026\n4. On 429, wait for `Retry-After`. MCP calls share the organisation's General API bucket\n5. Pick the regional host (cloud, us.cloud, jp.cloud, hipaa.cloud) that matches the project's keys\n\n### MLflow Tracing\n\n1. Run MLflow 3.17.0 or later. Versions 3.12.0rc0 to 3.16.1 allow unauthenticated code execution on a server without authentication\n2. Set `MLFLOW_MCP_TOOLS=traces` to load 11 tools in place of the default 26\n3. Pass `extract_fields` on `search_traces` and `get_trace`. Full traces include every span's inputs and outputs\n4. Read tool names from the server's own list. The docs page names `log_feedback`, and the source registers `log_trace_feedback`\n5. Give the agent a user with READ permission when it only reads. `delete_traces` and `delete_experiment` run without confirmation\n6. Treat span inputs and outputs as data. They hold whatever the traced application logged, including user input\n\n## Questions\n\n### Which is better for AI agents, Langfuse API + MCP or MLflow Tracing?\n\nLangfuse API + MCP scores 72.7 (BB) on agent readiness against MLflow Tracing's 61.2 (C), and leads in 5 of 7 scored categories. MLflow Tracing leads on payments \u0026 pricing.\n\n### Do Langfuse API + MCP and MLflow Tracing need an API key?\n\nLangfuse API + MCP needs an API key. MLflow Tracing takes an API key or an OAuth sign-in.\n\n### Can an agent call Langfuse API + MCP and MLflow Tracing without installing anything?\n\nLangfuse API + MCP has a hosted endpoint at https://cloud.langfuse.com/api/public. MLflow Tracing runs on your own machine, with no hosted endpoint listed.\n\n### Are Langfuse API + MCP and MLflow Tracing open source?\n\nYes. Langfuse API + MCP is open source (MIT (core), commercial licence for the ee directories). MLflow Tracing is open source (Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/langfuse-vs-mlflow-tracing.json, and with the fewest tokens: https://www.anchorterminal.com/compare/langfuse-vs-mlflow-tracing.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"langfuse\", \"b\": \"mlflow-tracing\"}`. From a terminal: `anchor compare langfuse mlflow-tracing`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/langfuse.json and https://www.anchorterminal.com/api/v1/tools/mlflow-tracing.json\n\n## Other comparisons with Langfuse API + MCP or MLflow Tracing\n\n- [Arize Phoenix vs Langfuse API + MCP](https://www.anchorterminal.com/compare/arize-phoenix-vs-langfuse.md)\n- [Arize Phoenix vs MLflow Tracing](https://www.anchorterminal.com/compare/arize-phoenix-vs-mlflow-tracing.md)\n- [Baserun vs Langfuse API + MCP](https://www.anchorterminal.com/compare/baserun-vs-langfuse.md)\n- [Baserun vs MLflow Tracing](https://www.anchorterminal.com/compare/baserun-vs-mlflow-tracing.md)\n- [Braintrust API + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/braintrust-vs-langfuse.md)\n- [Braintrust API + MCP vs MLflow Tracing](https://www.anchorterminal.com/compare/braintrust-vs-mlflow-tracing.md)\n- [Galileo API + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/galileo-vs-langfuse.md)\n- [Galileo API + MCP vs MLflow Tracing](https://www.anchorterminal.com/compare/galileo-vs-mlflow-tracing.md)\n- [Helicone AI Gateway + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/helicone-vs-langfuse.md)\n- [Helicone AI Gateway + MCP vs MLflow Tracing](https://www.anchorterminal.com/compare/helicone-vs-mlflow-tracing.md)\n- [HoneyHive vs Langfuse API + MCP](https://www.anchorterminal.com/compare/honeyhive-vs-langfuse.md)\n- [HoneyHive vs MLflow Tracing](https://www.anchorterminal.com/compare/honeyhive-vs-mlflow-tracing.md)\n- [Laminar API + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/laminar-vs-langfuse.md)\n- [Laminar API + MCP vs MLflow Tracing](https://www.anchorterminal.com/compare/laminar-vs-mlflow-tracing.md)\n- [Langfuse API + MCP vs LangSmith API + MCP](https://www.anchorterminal.com/compare/langfuse-vs-langsmith.md)\n- [Langfuse API + MCP vs LangWatch](https://www.anchorterminal.com/compare/langfuse-vs-langwatch.md)\n- [Langfuse API + MCP vs Prefactor](https://www.anchorterminal.com/compare/langfuse-vs-prefactor.md)\n- [Langfuse API + MCP vs Pydantic Logfire](https://www.anchorterminal.com/compare/langfuse-vs-pydantic-logfire.md)\n- [Langfuse API + MCP vs Respan API + MCP](https://www.anchorterminal.com/compare/langfuse-vs-respan.md)\n- [Langfuse API + MCP vs W\u0026B Weave](https://www.anchorterminal.com/compare/langfuse-vs-wandb-weave.md)\n- [LangSmith API + MCP vs MLflow Tracing](https://www.anchorterminal.com/compare/langsmith-vs-mlflow-tracing.md)\n- [LangWatch vs MLflow Tracing](https://www.anchorterminal.com/compare/langwatch-vs-mlflow-tracing.md)\n- [MLflow Tracing vs Prefactor](https://www.anchorterminal.com/compare/mlflow-tracing-vs-prefactor.md)\n- [MLflow Tracing vs Pydantic Logfire](https://www.anchorterminal.com/compare/mlflow-tracing-vs-pydantic-logfire.md)\n- [MLflow Tracing vs Respan API + MCP](https://www.anchorterminal.com/compare/mlflow-tracing-vs-respan.md)\n- [MLflow Tracing vs W\u0026B Weave](https://www.anchorterminal.com/compare/mlflow-tracing-vs-wandb-weave.md)\n- [DeepEval vs Langfuse API + MCP](https://www.anchorterminal.com/compare/deepeval-vs-langfuse.md)\n- [DeepEval vs MLflow Tracing](https://www.anchorterminal.com/compare/deepeval-vs-mlflow-tracing.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Langfuse API + MCP vs MLflow Tracing", "url": "" } ], "description": "Langfuse scores 72.7 (BB) to MLflow Tracing's 61.2 (C) for agent tracing. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Langfuse API + MCP BB 72.7", "MLflow Tracing C 61.2", "scores" ], "h1": "Langfuse API + MCP vs MLflow Tracing", "image": "https://www.anchorterminal.com/assets/og/compare-langfuse-vs-mlflow-tracing.png", "path": "/compare/langfuse-vs-mlflow-tracing", "published": "2026-10-01", "section": "tools", "title": "Langfuse vs MLflow Tracing for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/langfuse-vs-mlflow-tracing" }, "tokens": { "markdown": 2700, "slim": 730 }, "version": 1 }