Is StremAI MCP server safe?
Yes, with the usual care.
Passed every safety check we run. Maintained, authenticated, reachable, clean scan.
No critical or high findings in the latest scan.
How StremAI compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
1 medium
- Code scan2 source files scanned20/25
- Live reliabilityremote reachable in 384ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- mediumeval / new Function used
exec.evaldist/index.js: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
Overall 92/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 StremAI does
- Deja Vudeja-vu: local memory over the session histories of forty-three coding agents.not reviewedEstablishedA
- Concord MCPCross-harness communication and shared work-state for AI coding agents.not reviewedEstablishedA
- ClaudexorRoute coding work across Claude Code, Codex, Cursor, and OpenCode with shared context.not reviewedEstablishedA