Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
weam-ai/weam matches RepoRadar's tracked scope on the repository's own declared topics (agent-library, agents, ai, ai-agents, aiteamchat, claude), and is currently maintained: 221 stars and a push on 2026-10-12. This record states only what the repository states about itself; RepoRadar has not run it.
Where this stands now
weam-ai/weam ranks #1871 of 3275 tracked Radar items by composite score (4.9 against a section median of 4.9). The section currently carries 2159 Bronze, 645 Gold, 471 Silver.
Who should use it
Who should skip it
Pass on weam-ai/weam if its scope or audience does not match what your team is building right now.
About this signal
weam-ai/weam is tracked by RepoRadar as an MCP server in the Radar section. First seen 2026-10-12; the source record was last checked on 2026-10-12. The current verdict is 'watch' with a Bronze tier and unknown setup difficulty. The standout signals for weam-ai/weam 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 evidence RepoRadar captured from https://github.com/weam-ai/weam.
How this item is evaluated
The weam-ai/weam record combines a 4.9/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.