Is inboxmcp MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
What to know before installing
- highWrite-action tools reachable without authentication
How inboxmcp compares
Against every graded Email MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 81/100
- higher than 68% of 916 Email servers
- Tools that change things
- 85%
- typical: 25%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote Email server answers 100%
What its tools let an agent do: 2 read · 10 change · 1 send or post
Public scan report
scanner v0.1.10 · 2026-10-09 · same rubric, same numbers if you re-run it
1 high
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 939ms20/20
- Tool poisoning13 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 11 write-action tools with no auth3/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
Overall 81/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 inboxmcp does
- Voidmail Agent EmailLocal MCP tools for server-readable agent inboxes and sending to owner-approved recipients.not reviewedGrowingA
- e2a — email for AI agentsAuthenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.not reviewedEstablishedA
- e2a — email for AI agentsAuthenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.not reviewedEstablishedA