ReactUse
Coding · tested 2026-09-05 · re-test due 2026-12-04 · by the Hlido desk, not the vendor
In short: Mature, well-documented React hooks library (110+ hooks, TypeScript-first, SSR-safe) with a real MCP server so coding agents can query it — a solid developer utility whose 'agent' relevance is as a component, not an autonomous product.
5 PASS · 0 FAIL of 5 public-surface claims
Quick answer
ReactUse scores 74/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-09-05). STEADY (74): the documentation is thorough and well-structured, the API surface is large and specific, open-source with visible maintenance (changelog, blog), and it exposes an MCP server that makes it genuinely queryabl
ReactUse is a large, VueUse-inspired collection of production-oriented React hooks — the documentation lays out 110+ of them, organised into clear buckets (state, effect, element, browser, sensors), and the library advertises tree-shaking, SSR-safety and a TypeScript-first API. The surface is that of a settled open-source utility rather than a launch: an ordered hook index, a changelog, a blog, and adoption claims (Shopee, PDD, Ctrip) that read as credible for a library at 1k+ stars. What makes it relevant to an agentic register at all is that it ships an MCP server (the repo carries an MCP top-list badge and the `mcp` topic), which lets a coding agent look up and reason about the hooks programmatically. That is a legitimate but narrow kind of agent-relevance: ReactUse is a dependency a developer or a coding agent uses, not an agent that does work on its own. Judged as what it is — a developer library with an agent-readable surface — it is dependable and clearly presented. The caveats are the usual ones for this class: real quality lives in tree-shaking correctness, SSR edge-cases and per-hook stability, none of which a public-surface review exercises, and the adoption logos are asserted rather than independently confirmed here.
Why STEADY
STEADY (74): the documentation is thorough and well-structured, the API surface is large and specific, open-source with visible maintenance (changelog, blog), and it exposes an MCP server that makes it genuinely queryable by coding agents. Not higher because agent-relevance is component-level (a library, not an autonomous agent), per-hook correctness/SSR behaviour is untested at Tier-1, and the enterprise-adoption claims are unverified.
Public-surface checklist
- PASS Homepage loads (required)
- PASS Primary value prop (required) — '110+ Essential React Hooks Library for TypeScript'
- PASS Cta present (required) — 'Get Started'
- PASS Pricing or access — Open-source library, free; 'Buy me a coffee'/sponsor links
- PASS Evidence or demo — Full hook index and docs shown on site
What it does well
- Large, well-organised hook catalogue (110+) with a clear category index
- TypeScript-first, tree-shakable and SSR-safe by design
- Ships an MCP server so coding agents can discover and use the hooks programmatically
- Signs of active maintenance — changelog, blog, ordered docs
- Familiar mental model for anyone who knows VueUse
What it fails at
- It is a component library, not an autonomous agent — 'agent' relevance is indirect
- Per-hook correctness, tree-shaking and SSR edge behaviour are untested at Tier-1
- Enterprise adoption claims (Shopee/PDD/Ctrip) are asserted, not independently verified here
- No standalone runtime to behaviourally exercise as an agent
Best for
- React/TypeScript teams wanting a broad, maintained hooks toolkit
- Coding agents that can consume the MCP server to look up and apply hooks
- Projects that need SSR-safe, tree-shakable utilities out of the box
- Developers already comfortable with the VueUse pattern
Not recommended for
- Buyers looking for an autonomous agent or end-user product
- Teams that need an independently benchmarked performance guarantee before adopting
- Non-React stacks
Pricing & access
- Pricing findable on the public surfacePASS Open-source library, free; 'Buy me a coffee'/sponsor links (tested 2026-09-05)
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-09-05.
Related agents
Agent relevance
MCP SDK
A React hooks library consumed as a dependency; its MCP server lets a coding agent discover and apply hooks. Agent-relevance is component-level (something an agent uses), not an autonomous agent to drive.
Agent-friendly score: 5/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
scorecard.json · registry · methodology
Embed this trust badge
Markdown
[](https://hlido.eu/check/?agent=childrentime-reactuse)HTML
<a href="https://hlido.eu/check/?agent=childrentime-reactuse"><img src="https://hlido.eu/badge/childrentime-reactuse.svg" alt="Hlido trust score"></a>