The Index · Dev Tools & CI

Magic vs Use

These two are level on the tashan score (within 1 points), so the score does not decide it. The evidence rows below are where they differ. Both are measured the same way, on the same day, from public evidence only — so this is a comparison of two measurements rather than two marketing pages. How we measure ›

MagicUsewhat it means
tashan score8283upkeep + freshness, gated by adoption
Adoption evidence60k/wk25k/wkthe raw public signal the score came from
Last releaseactiveactivenpm publish or repo push
Upkeep86100cadence, maintainers, status
Expertise gradenot gradedsolidan LLM read of its own documentation against a fixed rubric
Security auditno known advisoriesno known advisoriesa summary — the full audit, free, is on each dossier
LicenceISCMIT
Maintainersmore than onemore than onebus-factor risk

Install either

Magic

claude mcp add 21st-dev-magic -- npx -y @21st-dev/magic

Use

claude mcp add use -- npx -y mcp-use

Neither score is a security verdict — "well maintained" and "nothing known is wrong" are different claims, which is why the audit is a separate row and never folded into the number. The full audit for each — the advisory ids, the version that fixes them and anything that runs at install time — is free on its own page: Magic · Use.

All ranked Dev Tools & CI ›

tashan Pro$6/mo

Both numbers above are today’s. Whichever you pick, the question that matters next is when it changes — and this page cannot know that. Pro keeps the series behind each capability, and names what to move to.

  • The whole series behind any row, back to the first day we measured it
  • The replacement, named — not just the news that something died
  • tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.