Is Quibbly LinkedIn Inbox MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
Public scan report
scanner v0.1.9 · 2026-09-22 · same rubric, same numbers if you re-run it
1 low
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 131ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenanceno repository listed3/15
- Maintainer identityno repository or website to verify2/10
Findings (1)
- lowNo source repository listed
maint.no-repo
Overall 67/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what Quibbly LinkedIn Inbox does
- MentionAgentLink building outreach from your agent: review drafts, send the batch, answer publisher replies.not reviewedGrowingA
- LinkedIn Content PlannerDraft, revise and review LinkedIn posts; a human approves each one before it goes live.not reviewedGrowingA
- ParseStreamSearch your brand's Reddit, X, LinkedIn, Quora and Hacker News mentions, and draft replies.not reviewedGrowingA