mcp-email-server
mcp0.10.1IMAP and SMTP via MCP Server
By ai-zerolab | 3 findings | Scanned 6/22/2026 | tooltrust-scanner/v0.3.19 | 255
Risk Summary
Safe With Normal ControlsDep Visibility is the main signal, but overall risk remains within an acceptable range.
Potential impact: This finding indicates the tool should be reviewed before it is trusted.
Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.
Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.
Security Findings (3)
Tool set changed silently at v0.10.1: 2 tool(s) added, 3 tool(s) removed without a version bump.
+ 2 added
check_creditsverify_emailโ 3 removed
email_readfolderinbox_listFix: The set of tools exposed by this server changed between scans of the same version โ a sign the package was silently updated without a version bump. Audit the changelog and all tool definitions before trusting this server. Pin to a specific commit hash rather than a floating version tag.
Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.
verify_emailcheck_creditsFix: Review and remediate the identified issue.
Scan this tool yourself
Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.
Install once, then scan any MCP server:
$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash$ tooltrust-scanner scan --server "npx -y mcp-email-server"Adjust the package name if your npm registry name differs from the tool ID. View source
Add badge to your README
Copy this Markdown to show your ToolTrust grade on GitHub.
[](https://github.com/AgentSafe-AI/tooltrust-directory)