# Langfuse API + MCP vs Overmind (slim)

> Langfuse scores 71.8 (BB) to Overmind's 58.5 (C) for agent tracing. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/langfuse-vs-overmind.md (~6,250 tokens) · this version ~3,780 tokens · JSON https://www.anchorterminal.com/compare/langfuse-vs-overmind.json · canonical https://www.anchorterminal.com/compare/langfuse-vs-overmind
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-02
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Langfuse API + MCP scores 71.8 (BB) on agent readiness against Overmind's 58.5 (C), and leads in 6 of 7 scored categories. Both do agent tracing.

- Langfuse API + MCP: BB 71.8, rank #130 of 1266 · https://www.anchorterminal.com/tools/langfuse.min.md
- Overmind: C 58.5, rank #650 of 1266 · https://www.anchorterminal.com/tools/overmind.min.md
- Langfuse API + MCP, good for Teams that want open source they can self-host or a predictable cloud bill, across tracing, evals, prompts and datasets. Ahead on Reliability, 80 against 23; Schema & documentation, 93 against 81; Security & auth, 77 against 70; Payments & pricing, 40 against 30; Maintenance & community, 88 against 76; Transparency & trust, 86 against 65. Also Agent-ready, a grade of BB or better; Free to start without a card.
- Overmind, good for A team that wants to go from agent traces to a fine-tuned small open model in one place, driven by a coding agent. Also No incidents deducted, where Langfuse API + MCP loses 5 points for them.

| Category | Langfuse API + MCP | Overmind |
| --- | --- | --- |
| Reliability (16%) | 80 | 23 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 93 | 81 |
| Agent ergonomics (13%) | 74 | 76 |
| Security & auth (14%) | 77 | 70 |
| Payments & pricing (10%) | 40 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 88 | 76 |
| Transparency & trust (7%) | 86 | 65 |

| Fact (where they differ) | Langfuse API + MCP | Overmind |
| --- | --- | --- |
| Vendor | Langfuse (ClickHouse) | Overmind Technology Ltd |
| Hosted endpoint | `https://cloud.langfuse.com/api/public` | `https://api.overmindlab.ai` |
| Auth | API key | OAuth or key |
| Licence | MIT (core), commercial licence for the ee directories | AGPL-3.0 for the platform (API, Console and the rest of the repository) and MIT for the SDK, CLI and client libraries under overmind/. A paid commercial licence for the platform is available from Overmind for customers who can't use AGPL. The hosted service is under Overmind's terms of 1 March 2026 |
| Tools exposed | 98 | 85 |
| Last release | 2026-10-29 | 2026-10-31 |
| Terms last updated | 2026-06-24 | 2026-03-01 |
| Privacy policy last updated | 2026-08-21 | 2026-10-03 |
| Terms restrict automated access | not found in the text | yes |
| Popularity | 35k stars, 3M npm/wk, 5.9M PyPI/wk | 732 stars |
| Agent reviews | 4/5 (2) | none |

Why the edge:
- Reliability, Langfuse API + MCP +57: Langfuse API + MCP 80 (incident.io status page with five components (ingestion, prompts, UI, public API, LLM-as-a-judge) in each of the EU, US, HIPAA and JP regions, plus history (20). The history page, re-read on 1 November, dates each component's impact. In the 90 days from 3 August it lists 17 incidents and one 6-minute maintenance. 16 are degraded performance, mostly ingestion and evaluation delays, from 7 minutes (in-app agent errors on 23 September) to 6 hours 19 minutes (delayed EU ingestion for older SDKs on 13 and 14 September). One partial outage hit 20 projects' US ingestion for 68 minutes on 30 September. Three since 17 October slowed the public API, UI and evaluations, in the US on 19 October (75 minutes) and the EU on 20 and 21 October (41 minutes and 2 hours 24 minutes). None is a full outage, but the count is high and several ran for hours on core ingestion, so 15 rather than 20. Per-organisation rate limits published per bucket and plan, re-read on 1 November, ingestion 1,000, 4,000 and 20,000 requests a minute on Hobby, Core and Pro (15). 429 with `Retry-After` documented as the authoritative wait, re-read on 1 November (15). Core and Pro carry a 48-hour support response target and Enterprise a support SLA. We found no uptime SLA (5). API and MCP are GA (10).); Overmind 23 (No status page. status.overmindlab.ai doesn't resolve, /status returns 404 and neither the site nor the docs link one (0). With no history to read, 5. No request rate limits for the REST API, MCP or OTLP ingest were found in the docs. The only pacing settings, `JEV_REQUESTS_PER_MINUTE` and `JEV_TOKENS_PER_SECOND`, are self-hosting configuration for the scoring model (0). No 429 or Retry-After guidance, but the docs give safe-retry rules in detail. Launches, uploads, pipeline runs and inference take a stable `request_key`, identical retries return the existing receipt, changed payloads conflict, and `run_evaluation` is named as not idempotent (8). The terms promise commercially reasonable efforts toward 99.5 per cent availability a month, with remedies only in an order form or separate SLA, so half (5). The site doesn't call the service beta, but the SDK is classed "3 - Alpha" on its package metadata and the public repository is seven weeks old (5). 0+5+0+8+5+5 = 23.)
- Transparency & trust, Langfuse API + MCP +21: Langfuse API + MCP 86 (MIT core with the ee directories under a commercial licence (27). Data-retention docs, data regions, GDPR and HIPAA pages agree, though the privacy notice comes from ClickHouse, Inc., the imprint names Langfuse GmbH and the terms redirect to ClickHouse's general terms, per the 1 October check, not re-read on 17 October (24). Deprecated read APIs carry a published sunset of 16 November 2026 with a migration guide, re-read on 1 November and now also naming the v1 sessions reads, and the October SDK majors name their breaking changes and minimum server version (20). Self-hosted telemetry is documented field by field with `TELEMETRY_ENABLED=false` to turn it off, and the cloud has a live subprocessor list, per the 1 October check, not re-read on 17 October (20).); Overmind 65 (Platform under AGPL-3.0 and SDK and CLI under MIT, both OSI licences, with a paid commercial licence as an option and a licensing page that says which code is which (30). The privacy policy of 3 October 2026 gives retention (subscription plus 30 days, deletion within 90 days, logs 365 days, backups 7 days), AWS eu-west-1 hosting and OAuth token lifetimes. The terms of 1 March 2026 still describe an earlier security product, say data stays in UK and EU data centres while the privacy policy names model, training and inference providers without locations, and incorporate a DPA that isn't published. The two documents agree on retention but not on the product (15). The terms promise 90 days' written notice before withdrawing a capability and 30 days' notice of material changes. No dated deprecation notices were found (8). SDK analytics are an opt-in extra with three documented off switches. The hosted MCP server reports to PostHog with payloads dropped, which the docs don't mention, and no named sub-processor list was found beyond AWS, though the docs name Modal, OpenRouter, Clerk and Stripe (12). 30+15+8+12 = 65.)
- Schema & documentation, Langfuse API + MCP +12: Langfuse API + MCP 93 (Public OpenAPI at cloud.langfuse.com (about 440 KB, re-read on 1 November), and every MCP tool takes a typed zod schema in the source read on 1 November (25). llms.txt and Markdown docs, with every page available as Markdown at `.md` (10). Tool descriptions say what to use each one for and how to size the result. `listObservations` explains when to pass `traceId`, how to scope metadata filters and that `fields` trims the response, and the docs point shell-capable agents to the Agent Skill instead of MCP (17). Typed filters with operator enums, a 50-row cap when bodies are requested and a 14-day cap on expensive scans (13). Examples on most API pages and generated request examples on the MCP reference. Error bodies are less fully documented (13). Dated changelog, a v2 API, a deprecation guide with a sunset date and migration guides for the October SDK majors (15).); Overmind 81 (The docs say each deployment serves its OpenAPI schema at `/api/schema/`, and the repository holds a generated client of 451 files under frontend/src/openapi. api.overmindlab.ai's robots.txt allows only /.well-known/, so the schema itself wasn't read. Every MCP tool takes a Pydantic input model with `extra="forbid"`, compiled to JSON Schema in overbae/services/mcp/catalog.py, read in the source at main on 31 October 2026 (25). llms.txt with 42 pages, llms-full.txt and Markdown for every page on Mintlify (10). Tool descriptions say what each does and what it doesn't ("Does not activate application routing", "no execution", "Passive: never starts provider work"), and the MCP reference warns that an inspection-style name doesn't mean zero cost. Some workbench descriptions are clipped to the point of being hard to parse (16). Typed inputs with Literal enums, length and range bounds, UUID formats and required fields (13). The docs have worked examples for the CLI, SDK, OTLP and inference, and document status classes (401, 402, 403, 404, 409) and structured MCP errors with code, message, retryability and field details, without a full error-code list (10). The MCP server exposes a contract version and a catalogue fingerprint at `overmind://interface/current`. The SDK changelog has one undated Unreleased section and no product changelog was found (7). 25+10+16+13+10+7 = 81.)
- Maintenance & community, Langfuse API + MCP +12: Langfuse API + MCP 88 (Server v4.72.0 tagged on 2026-10-29 (30). Nine v4 server tags from v4.64.0 on 19 October to v4.72.0 on 29 October, after 14 from 2 to 16 October, and v3.225.13 to v3.225.15 for the older line (20). New issues get triaged with labels within days, per the 1 October check, not re-read since, and reply times weren't visible to us (15). Python SDK v5.1.0 tagged on 2026-10-30 and JS SDK v6.1.0, current majors built for Langfuse v4 (15). CodeQL, Semgrep, Snyk and zizmor run in CI alongside the build pipeline. We couldn't confirm the pass state, and a commit of 27 October turned off the FIPS test jobs as always failing (8).); Overmind 76 (overmind 0.1.115 on PyPI on 2026-10-31, and the last commit on main the same day (30). 41 PyPI releases since 21 September 2026 and 24 git tags from v0.0.15 on 18 September to v0.1.23 on 30 October (20). github.com answered 403 to this session, so issues and pull request replies weren't read. 172 commits on main from eight people since 15 September, a Discord server and a support email (8). One official SDK, Python, current with the platform (10). Public CI workflows for the platform and SDK, Dependabot bumps merged on 28 October and a CI badge. We couldn't see the pass state (8). 30+20+8+10+8 = 76.)
- Payments & pricing, Langfuse API + MCP +10: Langfuse API + MCP 40 (No x402 or other machine payment (0). Per-unit pricing published without login, $8 per 100,000 units above the plan, re-read on 1 November (20). Hobby is free with 50,000 units a month and "No credit card required" (20). A person signs up in a browser to create keys. Free self-hosting isn't an agent route (0).); Overmind 30 (No x402 or other machine payment. Paid work spends prepaid credits, and `402` is documented only for insufficient credits (0). Plan prices, the credit rate ($0.01) and per-model "from" prices for training and serving are published without login (20). A Free plan with $50 of credits once exists, but neither the pricing page nor the docs say whether a card is needed, so half (10). A person signs up in a browser at console.overmindlab.ai. MCP OAuth with dynamic registration still needs a sign-in, and `create_api_key` needs an existing connection (0). Self-hosting under AGPL is free but runs on the operator's own Modal, OpenRouter, AWS and Hugging Face accounts, so it isn't scored as the hosted option. 0+20+10+0 = 30.)
- Security & auth, Langfuse API + MCP +7: Langfuse API + MCP 77 (Project-scoped key pairs over Basic auth, revocable, with organisation keys kept to admin APIs. Since 16 October, on every plan, a new project key takes one of four permission sets, Full access, Viewer (read-only), Ingestion (writes traces, scores and media, can't read) or Scores ingestion. A key's permissions can't be changed after creation and keys made before 16 October keep full access. Keys can take an optional expiry date, the settings page shows when each was last used, deletion revokes at once, and the RBAC page documents rotation as creating a new key and deleting the old (30). A Viewer key is read-only on the public API. The MCP server's source, re-read at v4.72.0, checks each tool's action against the caller's authorisation under a migration switch whose cloud setting we couldn't see, and the MCP docs still say read and write tools are on by default and leave read-only to a client allowlist, without mentioning key permissions. Annotations mark reads and destructive tools (14). Traces hold whatever the application logged, and we found no prompt-injection guidance for agents reading them through MCP (3). Audit logs on Enterprise only (10). Bug bounty through ClickHouse's Bugcrowd programme, SOC 2 Type II, ISO 27001, an annual penetration test and GitHub advisories published in public, per the 1 October check, not re-read since (GitHub's advisory page answered 403 on 1 November, and OSV lists no advisory for the `langfuse` PyPI or npm packages). langfuse.com/.well-known/security.txt returned 404 on 1 November (20).); Overmind 70 (API keys are account-scoped or pinned to one project, carry read, write or both, expire after 30 to 365 days or never, are shown once and show last use, and rotation is documented as replace then revoke. MCP also takes OAuth 2.1 from api.overmindlab.ai with PKCE S256, dynamic registration, a revocation endpoint, one-hour access tokens and rotating refresh tokens, with scopes `overmind:read` and `overmind:write`, the default being read. A key can only mint keys with the scope and permissions it holds, since 29 October 2026 (30). Read keys see only read tools over MCP, and the REST API refuses writes from a read-only key since the same commit (#263). Only two tools are destructive and lifecycle tools are allowlisted by name in the catalogue. The docs tell agents to confirm the GPU and rate with the user before starting a dedicated deployment, but there's no server-side approval step (15). The MCP prompts tell the agent to treat code, comments and data as untrusted content, and script output is labelled untrusted in resources. We found no guidance for agents reading trace inputs and outputs back (8). The Console's notification list shows what agents and the CLI did in a project, and `overmind://activity` returns it over MCP. No exportable audit log was found (10). SECURITY.md lists GitHub private vulnerability reporting and an email with acknowledgement within 3 business days. No security.txt on either host and no bug bounty. The terms claim an ISO 27001 certified management system and the site links a Vanta Trust Center, whose robots.txt disallows crawling, so neither was checked (7). 30+15+8+10+7 = 70.)