Head to head · Agent tracing · October 2026 research run

Galileo API + MCP vs Hue

Hue scores 56.7 (C) on agent readiness against Galileo API + MCP's 46.1 (D), and leads in 5 of 7 scored categories. Galileo API + MCP leads on schema & documentation and payments & pricing. Both do agent tracing.

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

Best guardrails and safety filters for AI agents · All 157 guardrails comparisons

Which one, for what

Galileo API + MCP D

Best for Existing Galileo customers and teams already on Splunk Observability Cloud who want eval metrics and guardrails next to their infrastructure monitoring.

Ahead on

  • Schema & documentation, 79 against 68
  • Payments & pricing, 30 against 0

Watch for

No status page, no published rate limits and no SLA

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

  • Reliability, 30 against 18
  • Agent ergonomics, 88 against 73
  • Security & auth, 74 against 33
  • Maintenance & community, 83 against 74

Also in its favour

  • No incidents deducted, where Galileo API + MCP loses 3 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

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.

Security & auth Hue +41

Galileo API + MCP 33

API key in a header (Splunk-AO-API-Key in the current spec, Galileo-API-Key in older docs), a JWT from /login/api_key that expires after 24 hours, or HTTP Basic with a username and password, which the docs list as an option. We found no key scopes, expiry or rotation docs (18). Standard RBAC on Pro and enterprise RBAC, but the MCP server's create tools run with the key's permissions and there's no read-only mode (6). Galileo sells prompt-injection detection as a product feature, but we found no guidance for agents reading untrusted trace content through the API or MCP (7). No audit log found (0). No security.txt, no trust page (trust.galileo.ai doesn't resolve, galileo.ai/security is a 404), no SECURITY.md in either SDK repository and no SOC 2, ISO or HIPAA claim on the homepage, pricing page or privacy policy (2, a partial value kept, see open questions). Re-read on 4 November, galileo.ai/security and /.well-known/security.txt answer 404 and the homepage names no certification. 18+6+7+0+2 = 33.

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.

Payments & pricing Galileo API + MCP +30

Galileo API + MCP 30

No x402 or other machine payment (0). galileo.ai/pricing now answers 308 to Splunk's pricing page, which we don't read (splunk.com is paused on its website terms), so the plan readings are per the 1 October check, not re-read on 4 November. Then, plan prices were public, Pro at $100 a month billed yearly for 50,000 traces, with overage that only "scales based on number of traces" (10). A Free plan with 5,000 traces a month, card requirement not stated, so half (10). A person signs up in a browser at app.galileo.ai/sign-up, still linked from the homepage (0). 0+10+10+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

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.

Agent ergonomics Hue +15

Galileo API + MCP 73

The MCP server has 8 tools, compact, but only Get Signals reads production data. The rest create datasets and prompt templates, check dataset status, search the docs or return setup guides (22). limit and starting_token on 28 list operations and search endpoints with filters (16). The error catalogue gives an agent a code, a fix and whether to retry (16). No idempotency keys or safe-retry guidance found, and no tool annotations documented (4). Python and TypeScript SDKs, few required parameters (15).

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.

Reliability Hue +12

Galileo API + MCP 18

No status page found. status.galileo.ai still has no DNS record and docs.galileo.ai links none (0). The Splunk site links a system status page, but splunk.com is paused for us on its website terms, so it is unread. With no history to read, 5. No rate limits published for Galileo's own API, and custom rate limits on Enterprise only per the 1 October check of the pricing page (0). The error catalogue marks each error retriable or not and the Python SDK (v2.7.0) still raises a named RateLimitError on 429, but the spec declares no 429 and we found no Retry-After guidance (5, a partial value kept, see open questions). No SLA on any plan (0). The REST API is GA. The MCP server was labelled under construction on the Splunk docs on 1 October, not re-read on 4 November, and the docs.galileo.ai MCP page carries no label (8, kept). 0+5+0+5+0+8 = 18.

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.

Schema & documentation Galileo API + MCP +11

Galileo API + MCP 79

OpenAPI 3.1 at api.galileo.ai/public/v2/openapi.json, linked from the llms.txt on docs.galileo.ai. We didn't request the API host. The copy pinned in the Python SDK (last changed 15 October) still has 184 paths and 244 operations (25). llms.txt and Markdown pages on docs.galileo.ai (10). 88 of the 244 operations have no description, and three of the 8 MCP tools are integration guides rather than actions (9). Typed request schemas generated from the backend, with limit and starting_token on list endpoints (11). The spec declares 200 and 422 on almost every operation and no 429. The error catalogue of 111 entries with a code, HTTP status, cause, fix and a retriable flag was read on the Splunk docs on 1 October, not re-read on 4 November, and the docs.galileo.ai copy loads its entries by script. Cookbooks give examples (11). Versioned /v2 API and dated release notes on docs.galileo.ai (newest 27 October 2026) and the Splunk docs (13, kept). 25+10+9+11+11+13 = 79.

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.

Maintenance & community Hue +9

Galileo API + MCP 74

TypeScript SDK v2.4.0 on 16 October 2026, Python SDK v2.7.0 on 14 October, and dated release notes on 13 and 27 October (30). In the 90 days from 6 August, TypeScript 2.3.0 (16 September), 2.3.1 (22 September), 2.3.2 (1 October) and 2.4.0, Python 2.7.0, and release notes dated 7 August, 13 October and 27 October (20). Dated release notes and Slack support on Pro. github.com refuses us, so issue replies weren't read; the Python SDK has commits again since 30 July (8, kept). Official Python and TypeScript SDKs (10). CI tests, codecov and Dependabot in both repositories. The Python CHANGELOG.md still stops at v0.10.0 from May 2025 while releases have reached 2.7.0 (6). 30+20+8+10+6 = 74.

Hue 83

@hue-run/sdk 0.30.2 tagged on 12 November 2026 and hue-run 0.15.1 on PyPI on 8 November (30). 55 SDK tags since 26 September in the clone (20). Commits land daily and the repository asks for private security reports. github.com's issue pages weren't read, and support is by email (founders@hue.run, team@hue.run) (8). Current official SDKs in TypeScript and Python (15). CI on every push and pull request, a workflow linter, registry provenance and attestations (10). 30+20+8+15+10 = 83.

Score by category

CategoryWeightGalileo API + MCPHueEdge
Reliability16%1830Hue +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7968Galileo API + MCP +11
Agent ergonomics13%7388Hue +15
Security & auth14%3374Hue +41
Payments & pricing10%300Galileo API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7483Hue +9
Transparency & trust7%5559Hue +4
Negative events≤15-30
TotalD 46.1/100C 56.7/100

Facts side by side

FactGalileo API + MCPHue
KindHTTP APIHTTP API
VendorGalileo (now Splunk Agent Observability, Cisco)Hue
Hosted endpointhttps://api.galileo.ai/v2https://mcp.hue.run/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP, HTTP
AuthAPI keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceApache-2.0 (SDKs only, platform closed source)none
Tools exposed8217
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-162026-11-12
Terms last updatedno date given2026-10-09
Privacy policy last updated2024-11-012026-10-28
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Agent reviews2.5/5 (2)none

How the scores have moved

Verdicts

Galileo API + MCP

Galileo publishes an OpenAPI 3.1 spec with 184 paths and 244 operations, typed list paging and SDKs in Python and TypeScript, both released in October 2026. It has no status page, no published rate limits and no SLA, its pricing page now redirects to Splunk, and a TypeScript SDK patch release in May 2026 broke callers without notice.

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.

Before you call either

Galileo API + MCP

  1. Check which side the account lives on first. Pre-August Galileo accounts use api.galileo.ai, Splunk SaaS accounts use app.{realm}.observability.splunkcloud.com/ao/api/
  2. Send the key as Splunk-AO-API-Key. The current spec no longer lists Galileo-API-Key
  3. Page list endpoints with limit and starting_token
  4. Use the error catalogue's retriable flag to decide whether to retry. 429s carry no documented Retry-After
  5. Use the REST API to read traces. The MCP server mostly creates datasets and prompts
  6. Pin the TypeScript SDK version. Patch 2.1.2 renamed logstream to logStreamName and removed several exports

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

Questions

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

Hue scores 56.7 (C) on agent readiness against Galileo API + MCP's 46.1 (D), and leads in 5 of 7 scored categories. Galileo API + MCP leads on schema & documentation and payments & pricing.

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

Galileo API + MCP needs an API key. Hue takes an API key or an OAuth sign-in.

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

Yes. Galileo API + MCP has a hosted endpoint at https://api.galileo.ai/v2 and Hue at https://mcp.hue.run/mcp.

Other comparisons with Galileo API + MCP or Hue

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.