Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for analytics engineers and data practitioners who want AI help on real warehouse work without re-briefing the model from scratch on every task.
Who should use it
Who should skip it
Move on from clarilayer/clarilayer if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
clarilayer/clarilayer is tracked by RepoRadar as a mcp server in the Developer Tools section. It was first seen on 2026-06-26 and last updated on 2026-06-26. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for clarilayer/clarilayer are workflow potential (9.6) and open-source/build quality (8.4), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned clarilayer/clarilayer a composite score of 8.1 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 57.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Connecting it to live warehouse or dbt context exposes business definitions and schema details to the service path you configure, so start with a non-production analytics project; The repo is MIT but the official product also runs a hosted signup and docs path, so teams should decide up front whether they want the open repo surface or the managed service surface; Persistent learned context can reinforce a wrong definition if the first correction is bad, so spot-check the remembered context against source SQL and dbt models.