linkedin-posts vs BadRooBot-test_m

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

Metriclinkedin-postsMCP Server BadRooBot-test_mMCP Server

Type: linkedin-postsMCP Server; BadRooBot-test_mMCP Server
Category: linkedin-postsWeb Scraping; BadRooBot-test_mWeb Scraping
GitHub stars: linkedin-posts0; BadRooBot-test_m0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: linkedin-postsNot yet assessed; BadRooBot-test_m57/100 · Fair
Community rating: linkedin-postsNo reviews yet; BadRooBot-test_mNo reviews yet
Last commit: linkedin-postsUnknown; BadRooBot-test_m313 days ago
Licence: linkedin-postsNone declared; BadRooBot-test_mNone declared
Official: linkedin-postsNo; BadRooBot-test_mNo
Source: linkedin-posts Repository; BadRooBot-test_m 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.