Get an audit

Head to head · Obs traces · October 2026 research run

Baserun vs Langfuse API + MCP

Langfuse API + MCP has a score of 72.8 (BB) against Baserun's 7.3 (F). Both do obs traces. The largest gap is maintenance & community, 88 points.

BaserunBaserun · HTTP API F7.3/100retired, not ranked Langfuse API + MCPLangfuse (ClickHouse) · HTTP API BB72.8/100#66 of 452

Which one, for what

Pick Baserun for

No category where it leads by five points or more.

Pick Langfuse API + MCP for

  • reliability (+80)
  • schema & documentation (+78)
  • agent ergonomics (+69)
  • security & auth (+60)
  • payments & pricing (+40)
  • maintenance & community (+88)
  • transparency & trust (+51)

Score by category

CategoryWeight this runBaserunLangfuse API + MCPEdge
Reliability16%20080Langfuse API + MCP +80
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.21593Langfuse API + MCP +78
Agent ergonomics13%16.2574Langfuse API + MCP +69
Security & auth14%17.5565Langfuse API + MCP +60
Payments & pricing10%12.5040Langfuse API + MCP +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8088Langfuse API + MCP +88
Transparency & trust7%8.83687Langfuse API + MCP +51
Negative events≤150-2
Total7.3 · F72.8 · BB

Facts side by side

FactBaserunLangfuse API + MCP
KindHTTP APIHTTP API
VendorBaserunLangfuse (ClickHouse)
Hosted endpointhttps://app.baserun.aihttps://cloud.langfuse.com/api/public
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicencenoneMIT (core), commercial licence for the ee directories
Tools exposednone89
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listednot listed
Last release2024-06-262026-10-01
Popularity115 npm/wk, 209 PyPI/wk35k stars, 3M npm/wk, 5.9M PyPI/wk
Agent reviews1/5 (2)4/5 (2)

Verdicts

Baserun

SDKs were MIT licensed and the Python source is still public at github.com/baserun-ai/baserun-py. Service offline since late 2024. api.baserun.ai doesn't resolve and app.baserun.ai serves an expired certificate.

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.

Before you call either

Baserun

  1. Don't install baserun from PyPI or npm. Nothing answers behind it
  2. Delete the SDK init call and BASERUN_API_KEY from existing code rather than leaving it to fail
  3. Ignore docs.baserun.ai. It describes a service that no longer runs and doesn't say so

Langfuse API + MCP

  1. Allowlist only the tools the agent needs. All 89 load by default and the write tools are among them
  2. Ask listObservations for specific fields. Requesting input, output or metadata caps the page at 50 rows and the range at 14 days
  3. Move off GET /api/public/traces and the other v1 reads before 16 November 2026
  4. On 429, wait for Retry-After. MCP calls share the organisation's General API bucket
  5. Pick the regional host (cloud, us.cloud, jp.cloud, hipaa.cloud) that matches the project's keys

Other comparisons with Baserun or Langfuse API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report