Is Likerts MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highRemote endpoint did not respond — Streamable HTTP error: Error POSTing to endpoint: {"error":"not_found"}
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
1 high
- Code scan10 source files scanned25/25
- Live reliabilityremote unreachable: Streamable HTTP error: Error POSTing to endpoint: {"error":"not_found"}0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableStreamable HTTP error: Error POSTing to endpoint: {"error":"not_found"}
Overall 65/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 Likerts does
- HasData ShopifyThe public product catalogue and collections of any Shopify storefront, as structured JSON.not reviewedGrowingA
DebugBundleDebugBundle MCP: runtime error reporting, incident response, health checks, and product analytics.not reviewedGrowingB- Loki ModeAutonomous spec-to-product coding-agent CLI with an MCP server exposing 36 tools over stdio.not reviewedEstablishedC