Item detail
github.com

js713-lab/sonic-match-mcp

js713-lab/sonic-match-mcp 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 8.4 out of 10.

Score4.2
Popularity0.0
Riskconditional
TierBronze
Score breakdown
Usefulness4.2
Novelty4.0
Momentum3.5
Maturity3.3
Open-source/build8.4
Evidence7.2
Workflow potential5.0
Setup ease5.0

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

Why it matters

js713-lab/sonic-match-mcp matches RepoRadar's tracked scope on the repository's own declared topics (ai-agents, bgm, ffmpeg, mcp, model-context-protocol, music-matching), and is currently maintained: 153 stars and a push on 2026-10-10. This record states only what the repository states about itself; RepoRadar has not run it.

Where this stands now

js713-lab/sonic-match-mcp ranks #3092 of 3231 tracked Radar items by composite score (4.2 against a section median of 4.9). The section currently carries 2115 Bronze, 645 Gold, 471 Silver.

Who should use it

Software developers Engineering teams

Who should skip it

Hold off on js713-lab/sonic-match-mcp until it graduates from watchlist status with stronger evidence.

About this signal

js713-lab/sonic-match-mcp is tracked by RepoRadar as an MCP server in the Radar section. First seen 2026-10-10; the source record was last checked on 2026-10-10. The current verdict is 'watch' with a Bronze tier and unknown setup difficulty. Across RepoRadar's eight signals, js713-lab/sonic-match-mcp is strongest on open-source/build quality (8.4) and evidence quality (7.2) and weakest on maturity (3.3) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar captured from https://github.com/js713-lab/sonic-match-mcp.

How this item is evaluated

The js713-lab/sonic-match-mcp record combines a 4.2/10 composite score with separate popularity (0.0), risk (conditional), and setup (unknown) 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

Discovered automatically from GitHub metadata and not installed, run, or reviewed by RepoRadar; Scout-staged and not hands-on tested by RepoRadar. Evidence level is Official; confirm the vendor's current install, pricing, and access terms before adopting.

Evidence links
Closest alternatives / related signals
ai-agents bgm ffmpeg mcp model-context-protocol music-matching python video
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 →

History begins 2026-10-10; trends appear after a second dated snapshot. 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 scoreTrend begins after a second recorded point.
Repository momentumTrend begins after a second recorded point.
GitHub stars (observed)Trend begins after a second recorded point.
GitHub stars153 exact observation
Versionv0.2.0
Last release2026-09-10T16:39:22Z
MaintenanceActive
Current riskConditional
Current verdictWatch
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-10-104.29.0153ConditionalWatchActive

Why the record changed

New entry

Newly added to RepoRadar's decision catalog.