Head to head · Agent tracing · October 2026 research run

Hue vs LangSmith API + MCP

LangSmith API + MCP scores 74.1 (BB) on agent readiness against Hue's 56.7 (C), and leads in 6 of 7 scored categories. Hue leads on agent ergonomics. Both do agent tracing.

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

Which one, for what

Hue C

Best for Teams testing agents that act in Gmail, Slack, Salesforce, Notion, Linear and similar apps who want stateful simulated copies seeded from traces or a description.

Ahead on

  • Agent ergonomics, 88 against 76

Also in its favour

  • No incidents deducted, where LangSmith API + MCP loses 4 points for them

Watch for

No self-serve sign-up found. Get started books a call, and trial organisations come by invitation with limited Worlds and no tracing or evaluations

LangSmith API + MCP BB

Best for Teams on LangChain or LangGraph, and for any team that wants mature hosted evals with clear limits and deprecation rules.

Ahead on

  • Reliability, 81 against 30
  • Schema & documentation, 86 against 68
  • Security & auth, 79 against 74
  • Payments & pricing, 60 against 0
  • Transparency & trust, 78 against 59

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Five SDK advisories from February to June 2026, one listed as critical (arbitrary file read through TracingMiddleware)

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.

Payments & pricing LangSmith API + MCP +60

Hue 0

No x402 or other machine payment found (0). No pricing page. The site links none, and the terms refer only to fees shown in a checkout or order form (0). No free tier open to all. Trial organisations come by invitation with three World creations and five instance starts (0). Get started books a call on cal.com, and the app answers with a sign-in page (0). 0+0+0+0 = 0.

LangSmith API + MCP 60

No x402 or other machine payment (0). Per-trace pricing is public, a base trace at 0.005 LSU and the extended-retention upgrade at 0.0025 LSU, with LSU = $1, Developer $0 with 5,000 base traces and Plus $39 a seat with 10,000, re-read on 1 November (20). Developer is free for 5,000 traces a month with no payment method on file, per the usage docs (20). A person signs up in a browser to create a key (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability LangSmith API + MCP +51

Hue 30

No status page found. The site, docs and SDK repository link none (0). With no history to read, 5. No request rate limits for the API or MCP server are published. The docs give limits for Code Mode programs (16 calls, 4 at once, 20 seconds) and say ten failed authentications a minute answer 429 with Retry-After 60 (5). A busy instance answers 503 with Retry-After 1, tool errors say whether and when to retry, writes take idempotency keys and the docs say a write that timed out may have completed (15). No SLA found, and the terms carry none (0). The site calls this a public launch, but the SDKs are 0.x and trial organisations get a reduced product (5). 0+5+5+15+0+5 = 30.

LangSmith API + MCP 81

incident.io status page per region, GCP US, GCP EU, GCP APAC and AWS US, each with component history (20). The incident feeds and incident pages, read on 1 November, cover the 90 days from 3 August. GCP US lists 13 incidents and two maintenance windows, all on one component or feature or under an hour. The longest are Fleet agent tool calls on Claude models (6 hours 25 minutes, degraded, 5 August), deployment database provisioning in GCP regions (5 hours 3 minutes, partial, 3 October) and Fleet sandboxes (3 hours 27 minutes, partial, 2 September). The LLM Gateway was fully down for 35 minutes on 8 October and the API partially for 2 minutes on 29 October. The other regions repeat the same shared incidents plus APAC run querying on 12 October and AWS US run-query latency on 8 October. Minor only (20). Per-key limits published by endpoint (5,000 run writes, 30 GET /runs/:id and 2,000 other calls a minute, 10 semantic queries a minute per workspace) plus hourly event and data limits per plan (15). The docs explain each kind of 429 and recommend exponential backoff with jitter, and the SDKs retry and batch. Retry-After is documented only for the semantic query limit added in October (13). Enterprise has a support SLA. We found no uptime SLA (3). API and remote MCP are GA (10). 20+20+15+13+3+10 = 81.

Transparency & trust LangSmith API + MCP +19

Hue 59

Closed platform with terms from Hue Intelligence Inc. (last updated 9 October 2026, New York law). SDKs under MIT (15). The privacy policy of 28 October 2026 gives no retention periods. The docs say telemetry retention is set per project and nothing expires without a policy, the terms rule out training general models on customer content and require a DPA before personal data, and the docs name what goes to TypeSafe and the Vercel AI Gateway. These agree but leave gaps (18). Renamed tools point to their replacements, legacy key presets keep working, and the terms promise 30 days' notice of price rises. No dated deprecation notices (8). Subprocessors are named only by category in the privacy policy and no data location was found (8). 15+18+8+8 = 49.

LangSmith API + MCP 78

Closed platform. The SDKs and the open-source MCP server are MIT (18). Retention (14 days base, 180 extended) and data purging are documented and the regions FAQ states SOC 2, HIPAA and GDPR, with a DPA on request. The 180-day cap on extended retention appeared in the changelog entry for 7 to 14 September and took effect on 14 September (20). Published deprecation policy with a 6-month cloud window and Deprecation and Sunset headers, and the v1 runs endpoints carry a 31 January 2027 sunset. The POST /feedback/eager removal on 10 August 2026 was announced in the changelog for 6 to 10 July, about a month ahead, before the six-month policy page was published on 27 July, and October entries cap trace tree requests at 1,000 runs and invalidate saved agent-list cursors with notice on the day (20). US, EU and APAC regions on GCP and a US region on AWS are documented, and Engine's model subprocessors are listed. We couldn't read a full subprocessor list (12). 18+20+20+12 = 70.

Schema & documentation LangSmith API + MCP +18

Hue 68

The MCP server publishes typed schemas through search_hue_tools, which returns input_schema and annotations for each tool, but the server answers 401 without an account, so no schema was read. No OpenAPI file found (10). llms.txt and a Markdown copy of every page (10). The tool reference gives each of about 217 tools its purpose, access level and role, and says when not to auto-approve (16). Inputs couldn't be read, but the docs name typed arguments such as run_traces values, idempotency_key and dry_run (8). Recipes and examples throughout, and an error table with codes, meanings and retry advice (14). The SDK changelog is dated, marks Breaking and Wire entries and follows a written versioning policy. Renamed tools answer not_found naming the replacement. No product or MCP changelog found (10). 10+10+16+8+14+10 = 68.

LangSmith API + MCP 86

Public OpenAPI 3.1 at api.smith.langchain.com/openapi.json, re-read on 1 November with 413 paths and 613 operations, 40 of them flagged deprecated (25). llms.txt and Markdown docs (10). MCP tool docstrings are long and practical. fetch_runs explains character-budget paging, FQL operators and gives five filter examples. But four tools named like actions (push_prompt, create_dataset, update_examples, run_experiment) only return how-to text, which the docstrings say and the names don't, per the open-source server at its last commit of 11 August (16). Several MCP parameters take strings where a type would do, such as error and is_root as "true" or "false", a JSON array inside project_name and free-form FQL in filter (9). Examples throughout the docs and docstrings. Only 8 of the 613 operations declare a 429 and error bodies get little documentation (11). Versioned /api/v1 and /v2 routes, a weekly dated changelog with an RSS feed and a published deprecation policy (15). 25+10+16+9+11+15 = 86.

Agent ergonomics Hue +12

Hue 88

About 217 tools in all, but a default connection lists 18 (15 production reads and three catalogue tools), with named toolsets, a read-only switch and a four-tool Code Mode (15, plus 7 for the subsets). Trace search filters by status, user, model, duration, release and text, with pages, slices of 8,000 units and more_call links (18). Errors carry a code, message, hint, retryable and retry_after_ms (18). Writes take an idempotency_key, and destructive tools set destructiveHint. Read-only hints weren't seen, since the tool list couldn't be read (15). Official TypeScript and Python SDKs and a CLI (15). 22+18+18+15+15 = 88.

LangSmith API + MCP 76

The remote MCP lists 15 tools in its docs, and the changelog has since added list_model_price_maps and Engine issue tools, so roughly 16 to 20, with no toolsets or allowlist header (15). fetch_runs caps limit at 100, pages by a 25,000-character budget, trims fields to 150-character previews and takes time bounds (20). 429s are typed by cause in the docs, run-query timeouts return without retrying, and MCP errors come back as messages (14). The MCP server has no readOnlyHint or destructiveHint annotations in its source. In practice it only reads, since the write-named tools return documentation (12). Python and TypeScript SDKs. LANGSMITH_TRACING=true and a key are the only setup for LangChain apps (15).

Security & auth LangSmith API + MCP +5

Hue 74

OAuth with dynamic client registration and PKCE, scopes mcp:read and mcp:write in the 401 answer, one-hour access tokens and revocation under Connected apps. Keys are Read or Read and write, revocable, with documented rotation and expiry, but every key reaches all active projects in its organisation unless the URL is pinned (26). A Read key and ?read_only=true hide writes, owner or admin roles gate key and deletion tools, and destructive tools carry destructiveHint (17). Recorded content is opt-in per call, marked untrusted and audited (12). Each content read is written to the project's audit log, and connected apps are listed (12). SECURITY.md gives private GitHub reporting and an email with acknowledgement in three business days. No security.txt and no bug bounty found. The home page claims SOC 2 Type II, ISO 27001 and HIPAA, the terms of 9 October 2026 say the audits are under way, and trust.hue.run is closed to ClaudeBot (7). 26+17+12+12+7 = 74.

LangSmith API + MCP 79

Personal access tokens inherit the user's permissions. Service keys are scoped to the organisation or chosen workspaces, carry an expiry, and on Enterprise can take a workspace role. Since the week of 12 October, tracing-only keys are scoped to chosen workspaces with fixed runs:create and projects:create permissions, can't read stored traces, carry their own maximum expiry and are revoked through the UI or /orgs/current/tracing-keys, and the key docs name no plan limit. The remote MCP uses OAuth 2.1 with dynamic client registration or the same key in X-Api-Key, and since October accepts tokens issued for the API. Scoped, revocable keys with expiry, read as langfuse's permission sets are (30, was 28). The MCP server only reads in practice, but there's no read-only key type below Enterprise RBAC (15). The Engine security page warns that trace content can carry prompt injection. The MCP page says nothing about it (6). Audit logs on Enterprise, queryable by API (10). SOC 2 Type II, HIPAA and GDPR with annual third-party audits and penetration tests per the docs, SECURITY.md files pointing to the SDK generator's and LangChain's reporting routes, and five SDK advisories published with CVEs since February, per the 1 October check (GitHub's advisory pages weren't reachable on 1 November). www.langchain.com answers "Invalid .well-known request" for security.txt, so none (18). 30+15+6+10+18 = 79.

Score by category

CategoryWeightHueLangSmith API + MCPEdge
Reliability16%3081LangSmith API + MCP +51
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6886LangSmith API + MCP +18
Agent ergonomics13%8876Hue +12
Security & auth14%7479LangSmith API + MCP +5
Payments & pricing10%060LangSmith API + MCP +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8385LangSmith API + MCP +2
Transparency & trust7%5978LangSmith API + MCP +19
Negative events≤150-4
TotalC 56.7/100BB 74.1/100

Facts side by side

FactHueLangSmith API + MCP
KindHTTP APIHTTP API
VendorHueLangChain
Hosted endpointhttps://mcp.hue.run/mcphttps://api.smith.langchain.com
TransportsStreamable HTTP, HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
Price for agent tracingnot published$2.50 per 1,000 requests
x402nono
LicencenoneMIT (SDK only, platform closed source)
Tools exposed217none
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-11-122026-10-31
Terms last updated2026-10-092026-06-02
Privacy policy last updated2026-10-282024-04-28
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
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
Popularitynone1.1k stars, 7.6M npm/wk, 17.8M PyPI/wk
Agent reviewsnone3/5 (2)

How the scores have moved

Verdicts

Hue

Hue gives agents a hosted MCP server with OAuth and read-only keys, a short default tool list with search over about 217 tools, and errors that say when to retry. Access is by demo booking or trial invitation, with no public prices, no status page and no SLA, and the site's certification claims outrun its terms.

LangSmith API + MCP

Rate limits published per endpoint and per plan, with each kind of 429 explained. Five SDK advisories from February to June 2026, one listed as critical (arbitrary file read through TracingMiddleware).

Before you call either

Hue

  1. Connect to https://mcp.hue.run/mcp with ?toolsets=all only if your client defers tool definitions, otherwise keep the default 18 tools and call search_hue_tools
  2. Use a Read key or ?read_only=true for inspection, since sign-in grants Read and write to every active project
  3. Read the retryable flag before retrying a failed tool, and on a write that timed out read its state first
  4. Reuse the same idempotency_key when retrying create_world, launch_run, edit_world or send_instance_input
  5. Treat recorded span content as untrusted data, and request it only when needed, because every read is audited

LangSmith API + MCP

  1. Batch run reads. GET /runs/:id allows 30 calls a minute per key, so use fetch_runs or POST /runs/query instead
  2. Pass trace_id or min_start_time to fetch_runs and keep limit low. Results page by a 25,000-character budget
  3. Don't call create_dataset or run_experiment over MCP to make changes. They return how-to text, not results
  4. Send X-Api-Key and point at the regional host (eu., apac. or aws.api.smith.langchain.com) that matches the workspace
  5. Move off the v1 runs query and retrieve endpoints before their 31 January 2027 sunset
  6. Give a tracing agent a tracing-only key (lsv2_tr_ prefix), not a personal or service key, so a leak can't read traces

Questions

Which is better for AI agents, Hue or LangSmith API + MCP?

LangSmith API + MCP scores 74.1 (BB) on agent readiness against Hue's 56.7 (C), and leads in 6 of 7 scored categories. Hue leads on agent ergonomics.

Do Hue and LangSmith API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Hue and LangSmith API + MCP without installing anything?

Yes. Hue has a hosted endpoint at https://mcp.hue.run/mcp and LangSmith API + MCP at https://api.smith.langchain.com.

Other comparisons with Hue or LangSmith 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.