Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams on AWS who need practical MCP integrations without hand-building service-specific glue.
Who should use it
Who should skip it
Move on from awslabs/mcp if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
awslabs/mcp is tracked by RepoRadar as a developer tool in the AI Infrastructure section. It was first seen on 2026-06-17 and last updated on 2026-06-17. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for awslabs/mcp are workflow potential (10.0) and practical usefulness (9.0), while setup ease (6.4) 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. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned awslabs/mcp a composite score of 9.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 93.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
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
AWS credentials are sensitive; strict IAM scoping is required before exposing tools to multi-agent flows.