Item detail
github.com

HKUDS/Vibe-Trading

RepoRadar surfaced HKUDS/Vibe-Trading — a developer tool — into the Radar section, where it sits at Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Score8.6
Popularity8.7
Riskmedium
TierGold
Score breakdown
Usefulness8.0
Novelty8.0
Momentum9.0
Maturity6.9
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease6.4

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

Why it matters

Useful for AI builders, fintech engineers, and quant-adjacent power users who want a real multi-agent trading harness with a built-in MCP integration, because Vibe-Trading combines the agent loop, the strategy catalog, and the backtester in one MIT-licensed repo, which means a single Claude/Codex session can both reason about the strategy and execute it on a connected broker instead of bolting

Who should use it

AI builders who want a multi-agent LLM trading harness with a built-in MCP server and backtester Fintech engineers prototyping agentic trading workflows against a real broker Quant-adjacent power users who want to chat with a strategy catalog and backtest it in one loop

Who should skip it

Skip HKUDS/Vibe-Trading if you cannot isolate its execution environment or audit what data it touches before connecting anything sensitive.

About this signal

HKUDS/Vibe-Trading is tracked by RepoRadar as a developer tool in the Radar section. First seen —; the source record was last checked on 2026-06-21. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. HKUDS/Vibe-Trading leads on workflow potential (10.0) and momentum (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 HKUDS/Vibe-Trading record combines a 8.6/10 composite score with separate popularity (8.7), risk (medium), 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 is a trading harness that can place real orders when wired to a live broker, so keep a manual review step in front of any live order placement and never run it unattended on production capital; It exposes an MCP server to your trading environment, so audit which tools the agent can call and lock down credentials to read-only keys for any sandbox testing.

Evidence links
Closest alternatives / related signals
trading algorithmic-trading multi-agent mcp backtesting llm fintech 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 →

44 dated snapshots retained from 2026-06-21 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.6 current · +0.0 net
Repository momentum9.6 current · +0.6 net
GitHub stars (observed)30,780 current · +9,588 net
GitHub stars30,780 exact observation
Versionv0.1.13
Last release2026-08-10T11:53:58Z
Maintenanceactive
Current riskmedium
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineModel Context Protocol

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.69.630,780mediumtry nowactive
2026-08-128.69.630,703mediumtry nowactive
2026-08-118.69.630,576mediumtry nowactive
2026-08-108.69.630,510mediumtry nowactive
2026-08-098.610.030,413mediumtry nowactive
2026-08-088.610.030,296mediumtry nowactive
2026-08-078.610.029,393mediumtry nowactive
2026-08-068.69.0Not recordedmediumtry nownot recorded
2026-08-058.69.0Not recordedmediumtry nownot recorded
2026-08-048.610.029,393mediumtry nowactive
2026-08-038.610.029,393mediumtry nowactive
2026-08-028.610.029,257mediumtry nowactive

Why the record changed

stars changed

Stars changed: 30703 → 30780.

stars changed

Stars changed: 30576 → 30703.

version changed

Version changed: v0.1.12 → v0.1.13.

stars changed

Stars changed: 30510 → 30576.

stars changed

Stars changed: 30413 → 30510.

stars changed

Stars changed: 30296 → 30413.

stars changed

Stars changed: 29393 → 30296.

stars changed

Stars changed: 29257 → 29393.

stars changed

Stars changed: 29058 → 29257.

stars changed

Source-observed stars changed: 28993 → 29058. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 28988 → 28993. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 28987 → 28988. This reports the retained observation delta and does not infer why the upstream change occurred.