vibe vs Steam Trends MCP

Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.

MetricvibeMCP Server Steam Trends MCPMCP Server

Type: vibeMCP Server; Steam Trends MCPMCP Server
Category: vibeGaming; Steam Trends MCPGaming
GitHub stars: vibe0; Steam Trends MCP0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: vibeNot yet assessed; Steam Trends MCPNot yet assessed
Community rating: vibeNo reviews yet; Steam Trends MCPNo reviews yet
Last commit: vibeUnknown; Steam Trends MCPUnknown
Licence: vibeNone declared; Steam Trends MCPNone declared
Official: vibeNo; Steam Trends MCPNo
Source: vibe Repository; Steam Trends MCPNot available

Highlighted cells win that row on an objective measure. Rows without a clear winner — category, licence, source — are left unmarked. A higher trust score means better auditability and maintenance, not safer code.