beacon-mcp vs dev-changes
Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.
- Type
- beacon-mcpMCP Server
- dev-changesMCP Server
- Category
- beacon-mcpVersion Control
- dev-changesVersion Control
- GitHub stars
- beacon-mcp0
- dev-changes0
- Trust score
- beacon-mcpNot yet assessed
- dev-changesNot yet assessed
- Community rating
- beacon-mcpNo reviews yet
- dev-changesNo reviews yet
- Last commit
- beacon-mcpUnknown
- dev-changesUnknown
- Licence
- beacon-mcpNone declared
- dev-changesNone declared
- Official
- beacon-mcpNo
- dev-changesNo
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.