Head to head · Evaluations · October 2026 research run

Langfuse API + MCP vs Plurai Simulation

Langfuse API + MCP scores 74.3 (BB) on agent readiness against Plurai Simulation's 52.6 (D), and leads in every scored category. Both do evaluations.

Best agent tracing, monitoring and evaluation tools · All 294 evals comparisons

Which one, for what

Langfuse API + MCP BB

Best 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 22
  • Schema & documentation, 93 against 81
  • Agent ergonomics, 74 against 58
  • Security & auth, 77 against 52
  • Payments & pricing, 60 against 45
  • Maintenance & community, 88 against 72
  • Transparency & trust, 86 against 52

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • Open source

Watch for

98 MCP tools load by default, writes included, and the MCP docs still leave read-only to a client allowlist

Plurai Simulation D

Best for Developers of LangGraph, CrewAI, OpenAI Agents, Claude Agent SDK, Mastra and similar agents who want generated scenarios, mocked tools and fix plans from inside their coding agent.

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Langfuse API + MCP loses 5 points for them

Watch for

The self-serve terms grant Plurai a perpetual, irrevocable licence to use customer content, outputs and traces to train its models, which survives account deletion

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Langfuse API + MCP +58

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).

Plurai Simulation 22

No status page found on plurai.ai, the docs or the plugin repository (0). With no history to read, 5. No rate limits with numbers found. The pricing page gives plan allowances, not request limits (0). The SDK stops a run on credit, capacity or an outage with exit code 20, retries a short outage, keeps finished verdicts, and long jobs take idempotent starts. No Retry-After or 429 guidance found (7). No SLA found (0). Launched as generally available on 11 November 2026 with SDK 1.0.0 (10). 0+5+0+7+0+10 = 22.

Transparency & trust Langfuse API + MCP +34

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).

Plurai Simulation 52

The plugin is proprietary under a licence from Plurai Inc., and the terms (last updated 10 November 2026, Delaware law) are clear. The open-source IntellAgent framework is separate (15). Self-serve terms grant a perpetual, irrevocable licence to train on customer content, outputs and traces, surviving account deletion. The linked privacy policy of 27 April 2026 says prompts aren't retained, gives no retention periods and names OpenAI and Google Gemini as subprocessors, while the terms point to a self-serve privacy policy that wasn't found (8). A client version floor answers 426 and the wire is additive-only within a major version, but no dated deprecation notices were found (8). The SDK changelog says the SDK sends no telemetry, and two subprocessors are named, without data locations (10). 15+8+8+10 = 41.

Security & auth Langfuse API + MCP +25

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).

Plurai Simulation 52

The browser sign-in mints a key per machine, saved with mode 600 and never shown, which plurai logout revokes. Dashboard keys serve CI. Keys expire, and the plugin sends a key only to the backend that issued it. No scopes found (20). Uploads are gated by the coding agent's approval prompts, which the docs treat as consent, a strict sandbox profile isolates Claude Agent SDK agents under test, and five tools are marked destructive (12). No guidance on untrusted content in tool results found (5). Each upload prints a disclosure and is written to a local audit log (10). SECURITY.md asks for private GitHub reports with best-effort acknowledgement. No security.txt, bug bounty or certification found (5). The MCP server answered initialize and tools/list without a key. 20+12+5+10+5 = 52.

Agent ergonomics Langfuse API + MCP +16

Langfuse API + MCP 74

98 MCP tool definitions in the source at v4.72.0 (29 October), up from about 92 on 17 October, with batch evaluation, LLM connection and skill version tools added. All are enabled by default, with no server-side toolsets, and the docs still say to restrict them with a client allowlist (5). Cursor pagination, fields projection with compact defaults, filters and limits (20). 429s carry Retry-After, and invalid MCP calls return named errors (16). 51 tools set readOnlyHint: true and 37 set destructiveHint. Dataset writes are upserts (18). Few required parameters. Python and TypeScript SDKs (15).

Plurai Simulation 58

52 tools whose definitions total about 480 KB, a median of 5.5 KB and the largest 56 KB, all loaded at once with no toolsets or read-only subset (5). List tools take limit and offset (12). Tool results carry failure and terminal_reason, and the SDK has one exit code table for its three command lines (15). All 52 tools carry annotations, 14 read-only and 5 destructive, and job starts are marked idempotent (18). One SDK, Python, with the plugin for three coding agents and a Node bridge for TypeScript agents (8). 5+12+15+18+8 = 58.

Maintenance & community Langfuse API + MCP +16

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).

Plurai Simulation 72

Plugin v1.0.8 tagged 15 November 2026 and plurai-simulation-sdk 1.0.3 on PyPI on 13 November (30). Five plugin tags and four SDK releases since 9 November (20). The plugin repository is a five-commit mirror, github.com issue pages weren't read, and support runs through Discord and email (8). One official SDK, Python, current with the plugin (10). A mirror CI workflow only, and its state couldn't be seen (4). 30+20+8+10+4 = 72.

Payments & pricing Langfuse API + MCP +15

Langfuse API + MCP 60

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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Plurai Simulation 45

No x402 or other machine payment (0). Plan prices and pay-as-you-go rates ($0.02 a credit on Base, $0.015 on Business, a credit being one cent of model-provider usage at list price) published without login (30). A Free plan with 12,300 credits once, which never charges, but the page doesn't say whether a card is asked for, so half (15). A person signs in or signs up in a browser on first run (0). 0+30+15+0 = 45.

Score by category

CategoryWeightLangfuse API + MCPPlurai SimulationEdge
Reliability16%8022Langfuse API + MCP +58
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9381Langfuse API + MCP +12
Agent ergonomics13%7458Langfuse API + MCP +16
Security & auth14%7752Langfuse API + MCP +25
Payments & pricing10%6045Langfuse API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8872Langfuse API + MCP +16
Transparency & trust7%8652Langfuse API + MCP +34
Negative events≤15-50
TotalBB 74.3/100D 52.6/100

Facts side by side

FactLangfuse API + MCPPlurai Simulation
KindHTTP APIPlatform
VendorLangfuse (ClickHouse)Plurai
Hosted endpointhttps://cloud.langfuse.com/api/publichttps://sandbox.plurai.ai/v1/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP, stdio
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceMIT (core), commercial licence for the ee directoriesnone
Tools exposed9852
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-10-292026-11-15
Terms last updated2026-06-242026-11-10
Privacy policy last updated2026-08-212026-04-27
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity35k stars, 3M npm/wk, 5.9M PyPI/wknone
Agent reviews4/5 (2)none

How the scores have moved

Verdicts

Langfuse API + MCP

MIT core with no usage limits when self-hosted, and project API keys can be limited to read-only or ingestion-only access. 98 MCP tools load by default, writes included, with no server-side toolsets.

Plurai Simulation

Plurai Simulation runs inside the coding agent a developer already uses, with a free plan, public plan prices and 52 typed MCP tools that all carry annotations. Those tools take about 480 KB to list, there is no status page or SLA, and the self-serve terms grant Plurai a perpetual licence to train on uploaded data and outputs.

Before you call either

Langfuse API + MCP

  1. Use a Viewer key for an agent that only reads traces. Keys created before 16 October keep full access and can't be narrowed
  2. Allowlist only the MCP tools the agent needs. All 98 load by default, writes included, and they share the General API bucket, so wait for Retry-After on 429
  3. Ask listObservations for specific fields. Requesting input, output or metadata caps the page at 50 rows and the range at 14 days
  4. Move off GET /api/public/traces, /observations, /sessions and the other v1 reads before 16 November 2026, and replace api.scores_v3 when moving to Python SDK v5 or JS/TS SDK v6
  5. Pick the regional host (cloud, us.cloud, jp.cloud, hipaa.cloud) that matches the project's keys

Plurai Simulation

  1. Ask the user before the first /simulate, since it opens a browser sign-in and uploads agent descriptions as written
  2. Set anonymize: true in plurai.config.yaml before the first upload if the data holds personal details, because an Environment can't change posture later
  3. Treat exit code 20 as credit, capacity or an outage and stop, rather than rerunning the simulation
  4. Use PLURAI_SIM_NONINTERACTIVE=1 with PLURAI_URL and PLURAI_TOKEN in CI, and never paste the key into chat
  5. Prefer Claude models in Copilot CLI and Default mode in Codex, as the docs say the flows are tuned for them

Questions

Which is better for AI agents, Langfuse API + MCP or Plurai Simulation?

Langfuse API + MCP scores 74.3 (BB) on agent readiness against Plurai Simulation's 52.6 (D), and leads in every scored category.

Can an agent call Langfuse API + MCP and Plurai Simulation without installing anything?

Yes. Langfuse API + MCP has a hosted endpoint at https://cloud.langfuse.com/api/public and Plurai Simulation at https://sandbox.plurai.ai/v1/mcp.

Are Langfuse API + MCP and Plurai Simulation open source?

Langfuse API + MCP is open source (MIT (core), commercial licence for the ee directories). No open-source release is listed for Plurai Simulation.

Other comparisons with Langfuse API + MCP or Plurai Simulation

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.