Item detail
github.com

dhruvanbhalara/flutter_agent_lens

dhruvanbhalara/flutter_agent_lens is a developer tool that RepoRadar is tracking in its Developer Workflow section, currently rated Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.8 out of 10.

Score8.3
Popularity1.0
Riskconditional
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum7.0
Maturity6.5
Open-source/build8.4
Evidence7.2
Workflow potential9.8
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for Flutter developers who want an agent to debug and profile a live app with real runtime evidence rather than just static code context and copied console output.

Who should use it

Flutter developers debugging jank, memory leaks, or rebuild churn Mobile teams that want MCP-native runtime inspection instead of log-copying loops Agent-tool builders studying how to expose live app diagnostics safely Developers validating whether agents can help with profiling and layout regressions in real apps

Who should skip it

Pass on dhruvanbhalara/flutter_agent_lens if its scope or audience does not match what your team is building right now.

About this signal

dhruvanbhalara/flutter_agent_lens is tracked by RepoRadar as a developer tool in the Developer Workflow section. First seen 2026-07-01; the source record was last checked on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. dhruvanbhalara/flutter_agent_lens leads on workflow potential (9.8) and practical usefulness (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The dhruvanbhalara/flutter_agent_lens record combines a 8.3/10 composite score with separate popularity (1.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

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

It exposes live runtime internals like memory state, network traffic, logs, and widget trees to the connected MCP client, so first evaluation should use a non-sensitive debug build; The server can trigger app-side actions such as scroll behaviors and hot reload workflows, so keep the first test on a disposable device or simulator rather than a production-like environment.

Evidence links
Closest alternatives / related signals
flutter mcp debugging profiling dart mobile mit
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

34 dated snapshots retained from 2026-07-01 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.3 current · +0.0 net
Repository momentum9.0 current · +2.0 net
GitHub stars (observed)45 current · +5 net
GitHub stars45 exact observation
Versionv1.7.3
Last release2026-08-12T18:10:58Z
Maintenanceactive
Current riskconditional
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.39.045conditionaltry nowactive
2026-08-128.39.045conditionaltry nowactive
2026-08-118.39.045conditionaltry nowactive
2026-08-108.39.045conditionaltry nowactive
2026-08-098.39.045conditionaltry nowactive
2026-08-088.39.045conditionaltry nowactive
2026-08-078.39.043conditionaltry nowactive
2026-08-068.37.0Not recordedconditionaltry nownot recorded
2026-08-058.37.0Not recordedconditionaltry nownot recorded
2026-08-048.39.043conditionaltry nowactive
2026-08-038.39.043conditionaltry nowactive
2026-08-028.39.042conditionaltry nowactive

Why the record changed

version changed

Version changed: v1.7.2 → v1.7.3.

version changed

Version changed: v1.7.0 → v1.7.2.

stars changed

Stars changed: 43 → 45.

stars changed

Stars changed: 42 → 43.

version changed

Version changed: v1.6.2 → v1.7.0.

stars changed

Stars changed: 40 → 41.

version changed

Version changed: v1.6.0 → v1.6.2.