Is Backlot 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 Backlot compares
Against every graded Email MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 86/100
- higher than 79% of 914 Email servers
Public scan report
scanner v0.1.10 · 2026-10-24 · same rubric, same numbers if you re-run it
1 medium
- Code scan119 source files scanned20/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (1)
- mediumsubprocess with shell=True
exec.shell-truebacklot-0.1.0/pyproject.toml: … # eval "S602", # subprocess with shell=True "S604", # a call with shell=True …
Overall 86/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 Backlot does
- Connected AppsRead Gmail, search GitHub, update Sheets, and post to Slack through Composio.not reviewedEstablishedA
- PipesHubPermissioned search and cited answers over Slack, Drive, Gmail, Jira, and 50+ workplace sources.not reviewedEstablishedC
- WorkspaceGoogle Workspace MCP server for Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Chat.not reviewedWidely usedA
