Is Litmus MCP server safe?

Probably. Read the findings first.

C61/100grade C

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": {"code": "404", "message": "The deployment could not be found on Vercel."}}

How Litmus compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 61/100; higher than 16% of 48,255 servers
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break
Uptime: 25%; of our recent checks; the typical remote server answers 100%

What its tools let an agent do: 3 read

scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it

1 high

Code scan16 source files scanned25/25
Live reliabilityremote unreachable: Streamable HTTP error: Error POSTing to endpoint: {"error": {"code": "404", "message": "The deployment could not be found on Vercel."}}0/20
–Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 101 days ago8/15
Maintainer identityregistry namespace matches repository owner7/10

highRemote endpoint did not respondreliability.unreachable
Streamable HTTP error: Error POSTing to endpoint: {"error": {"code": "404", "message": "The deployment could not be found on Vercel."}}

Overall 61/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON