web-recon-agent vs cobbles

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

Metricweb-recon-agentMCP Server cobblesMCP Server

Type: web-recon-agentMCP Server; cobblesMCP Server
Category: web-recon-agentSecurity; cobblesSecurity
GitHub stars: web-recon-agent0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: web-recon-agentNot yet assessed; cobblesNot yet assessed
Community rating: web-recon-agentNo reviews yet; cobblesNo reviews yet
Last commit: web-recon-agentUnknown; cobblesUnknown
Licence: web-recon-agentNone declared; cobblesNone declared
Official: web-recon-agentNo; cobblesNo
Source: web-recon-agent Repository; cobbles Repository

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.