What did Hlido score yutu?

yutu scored 71/100 (STEADY) in Hlido's independent, hands-on review.

How much does yutu cost?

Hlido recorded the pricing model as: Open source. Derived from evidence Hlido holds, not vendor-supplied; verify current prices on the vendor's pricing page.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

yutu

Name: yutu review
Item: yutu
Rating: 71
Author: Hlido Editor

Marketing & Content · tested 2026-08-14 · by the Hlido desk, not the vendor

In short: A genuinely tri-modal YouTube toolkit — CLI, MCP server and A2A agent from one binary — whose install path is verifiable and whose 'autopilot' claim is not.

Visit yutu → scorecard.json

Quick answer

yutu scores 71/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-14). STEADY because the verifiable core — a broad, well-organised YouTube automation surface exposed through three interfaces with real install paths and an OSI licence — is solid and immediately usable. Pricing: Open source (free entry point documented).

Hlido Editor · 2026-08-14

yutu is unusual in this crop for shipping three interfaces over one codebase: a 30+ command CLI, an MCP server you drop into Claude Desktop, Cursor or OpenCode, and an A2A agent mode. The public surface backs the mechanical claims well — brew, winget and a curl installer are all published, the MCP config snippet is copy-pasteable, and the resource list (video, playlist, caption, thumbnail, membership, super-chat, i18n, abuse report) reads like it was generated from the YouTube Data API surface rather than from a marketing brainstorm. Apache-2.0 with the repo linked from the fold. Where it thins out is exactly where the headline promise lives. 'Grows your YouTube channel on autopilot' and 'autonomous multi-agent system' are the two load-bearing claims, and neither is evidenced anywhere on the public surface — no demo of the agent running, no description of what the agents decide, no before/after. What is demonstrably shipped is comprehensive YouTube API automation, which is a useful and honest product; the autonomy layer on top is asserted. For a buyer, the CLI and MCP surface is the part to evaluate on, and it is strong. Treat the agent mode as unproven until you run it.

Why STEADY

STEADY because the verifiable core — a broad, well-organised YouTube automation surface exposed through three interfaces with real install paths and an OSI licence — is solid and immediately usable. Held below the top band because the product's own headline claim (autonomous channel growth) has no public evidence behind it, and because there is no demo or docs surface deep enough to check what the agent mode actually does.

What we saw

2 screenshots captured by the Hlido engine during the reviewed run (run-429d75745e16933f-yutu-ifor-dev). Our own captures — not vendor marketing material.

yutu — run screenshot 1 (home.png) — home.png

yutu — run screenshot 2 (page__usage.png) — page__usage.png

What it does well

Three interfaces (CLI, MCP server, A2A agent) from a single install — rare and genuinely useful
Install paths published for macOS, Windows and Linux, all copy-pasteable
MCP config snippet given verbatim, with named clients (Claude Desktop, OpenCode, Cursor)
Resource coverage is broad and specific — 20+ YouTube entity types enumerated, not hand-waved
Apache-2.0, repo linked prominently from the landing page

What it fails at

'Autopilot' / 'autonomous multi-agent system' is asserted with zero public evidence — no demo, no decision description
No documentation surface beyond the landing page; the four-step quickstart is the whole story
No description of how OAuth credentials are stored or scoped, despite the tool requiring full channel write access
No changelog, roadmap or release cadence signal on the public surface
The A2A agent invocation is shown as a bare flag string with no explanation of the modes it takes

Red flags

The headline promise ('grows your YouTube channel on autopilot') is the single least-evidenced thing on the page, which inverts the usual expectation that the biggest claim carries the most proof.
The tool requires OAuth credentials with broad YouTube write scope, and the public surface says nothing about how those credentials are handled.

Best for

Creators and channel operators who want scriptable YouTube automation and are comfortable in a terminal
Developers wiring YouTube management into an AI editor over MCP
Teams replacing brittle hand-rolled YouTube Data API scripts with a maintained CLI
CI/CD publishing pipelines (GitHub Actions and Docker are both named)

Not recommended for

Buyers who need the autonomous growth claim to be real before committing — it is unevidenced
Non-technical creators; every documented path starts at a shell prompt
Anyone needing a documented data-handling or credential-storage posture before granting channel write access

Pricing & access

ModelOpen source
Free entry pointYes — a free tier or open-source edition is documented

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-11.

Compared to

n8n depth-vs-breadth
n8n is the general-purpose automation platform with a YouTube node among hundreds; yutu is YouTube-only but far deeper on that one API. Choose n8n if YouTube is one step in a wider workflow, yutu if YouTube IS the workflow.
Zapier no-code-vs-developer
Zapier is no-code and hosted; yutu is a self-hosted binary you authenticate yourself. Zapier wins on accessibility, yutu on API coverage and cost (free).

Agent relevance

CLI MCP Behavioral-testable

Agentic-Commerce Readiness 51/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

First-class MCP server with a published stdio config, plus an A2A agent mode. An agent can drive the full YouTube entity surface through named tools. The CLI is equally scriptable. This is one of the more agent-addressable tools in its category — the limiting factor is credential setup, not interface availability.

Agent-friendly score: 8/10

Evidence

Homepage publicly accessible and value proposition clearly stated — source (2026-08-14) verified
Pricing page discoverable in 2 clicks from homepage — source (2026-08-14)
Documentation or live demo accessible without login — source (2026-08-14)
Integration list or supported frameworks documented — source (2026-08-14) verified
Authentication / data handling claims publicly stated — source (2026-08-14)

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-2+editorial-narrative-v2 · Methodology version 2026.08 ·

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/eat-pray-ai-yutu.svg)](https://hlido.eu/check/?agent=eat-pray-ai-yutu)

HTML

<a href="https://hlido.eu/check/?agent=eat-pray-ai-yutu"><img src="https://hlido.eu/badge/eat-pray-ai-yutu.svg" alt="Hlido trust score"></a>