Item detail
github.com

OpenComputerUse

OpenComputerUse is an MCP server in RepoRadar's Radar section, holding Bronze tier and a 'watch' verdict. Its strongest signal is open-source/build quality, scored 7.4 out of 10.

Score6.2
Popularity9.0
Riskconditional
TierBronze
Score breakdown
Usefulness6.2
Novelty4.7
Momentum3.5
Maturity4.8
Open-source/build7.4
Evidence7.2
Workflow potential6.6
Setup ease6.5

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

Why it matters

Backgrounded computer use avoids stealing the screen from the human, which is the main usability blocker for desktop agents.

Where this stands now

OpenComputerUse ranks #1119 of 3231 tracked Radar items by composite score (6.2 against a section median of 4.9). The section currently carries 2115 Bronze, 645 Gold, 471 Silver. RepoRadar has retained observations for this record since 2026-10-08 (2 days in the current window).

Who should use it

Builders Power users

Who should skip it

Consider OpenComputerUse lower priority if you already have a working solution in this category.

About this signal

OpenComputerUse is tracked by RepoRadar as an MCP server in the Radar section. First seen 2026-10-08; the source record was last checked on 2026-10-08. The current verdict is 'watch' with a Bronze tier and review needed setup difficulty. The standout signals for OpenComputerUse are open-source/build quality (7.4) and evidence quality (7.2), while momentum (3.5) trails — that balance shapes where it fits best. 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 OpenComputerUse record combines a 6.2/10 composite score with separate popularity (9.0), risk (conditional), and setup (review needed) signals. See the scoring methodology for the current weights and evidence definitions.

Questions worth asking before you adopt this

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

Conditional risk: review permissions, runtime environment, and data boundaries before production use.

Evidence links
Closest alternatives / related signals
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-10-10T17:09:29.745535Z.

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 →

2 dated snapshots retained from 2026-10-09 through 2026-10-10; 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 score6.2 current · +0.0 net
Repository momentum9.0 current · +0.0 net
GitHub stars (observed)13 current · +1 net
GitHub stars13 exact observation
Versionv0.6.0
Last release2026-10-09T20:26:54Z
MaintenanceActive
Current riskConditional
Current verdictWatch
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-10-106.29.013ConditionalWatchActive
2026-10-096.29.012ConditionalWatchActive

Why the record changed

Stars change

Stars changed: 12 → 13.

Version change

Version changed: v0.5.0 → v0.6.0.

Stars change

Stars changed: 10 → 12.

New entry

Newly added to RepoRadar's decision catalog.