Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 2
- 4 1
- 3 3
- 2 0
- 1 0
Trust in production
- Trust it - 50%
- With caveats - 17%
- Wouldn't - 33%
67% would recommend this server
How reviewers scored it
- Setup & docs 3.7
- Auth experience 3.7
- Reliability 3.8
- Maintainer responsiveness 3.7
Why it got a C
The MCP server for mails-agent (mails0), an MIT-licensed email service for agents that extends chekusu/mails and can be self-hosted on Cloudflare Workers. On first use it creates a 72-hour receive-only mailbox, so an agent can read mail and pull verification codes with no sign-up. Sending, managing domains or webhooks, and downloading attachments need a claimed permanent mailbox. The key sits in ~/.mails/config.json (mode 0600) and is never returned to the model. No advisories on record and no shell-out. Every email it reads was written by a stranger, so treat inbox content as untrusted input. Biggest deduction: one person maintains it with no commit since 26 July 2026, and a claimed mailbox uses a single unscoped key for read, send and delete.
How to connect
// .cursor/mcp.json
{ "mcpServers": { "mails-agent": { "command": "npx", "args": ["-y", "mails-agent-mcp"] } } }claude mcp add mails-agent -- npx -y mails-agent-mcp// claude_desktop_config.json
{ "mcpServers": { "mails-agent": { "command": "npx", "args": ["-y", "mails-agent-mcp"] } } }Is mails-agent MCP Server (mails0) safe?
Is mails-agent MCP Server (mails0) safe to use?
mails-agent MCP Server (mails0) grades C (usable with care). Login is required, but access is coarse: one sign-in or key covers more than your agent needs, so grant the narrowest account you can. Updates are occasional, so fixes may be slow to arrive. It runs locally over stdio, so it acts with your machine's access.
Does mails-agent MCP Server (mails0) have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does mails-agent MCP Server (mails0) support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Developer Tools
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
- A Dynatrace Remote MCP ServerDynatrace's hosted MCP server, running inside your Dynatrace SaaS environment, to run and explain DQL, look into problems, vulnerabilities and Kubernetes events, and forecast time series.
- A GitHub MCP ServerOfficial GitHub server for repos, issues, pull requests, Actions, and code security, hosted or local.
- A GitLab MCP ServerGitLab's built-in MCP server for projects, merge requests, work items, code, and CI pipelines, on GitLab.com or your own instance.
Embed this badge
[](https://trustedmcp.io/servers/mails-agent-mcp)<a href="https://trustedmcp.io/servers/mails-agent-mcp"><img src="https://trustedmcp.io/badge/mails-agent-mcp.svg" alt="TrustedMCP grade C" height="80"></a>Community reviews
Fine once configured properly
I like it, with reservations. Self-hosting it was straightforward and I like keeping the data on our side. You create a token and pass it in. Scope it narrowly, that is the main thing.
Used for Debugging sessions in Cursor
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Clean integration, sensible permissions
Hooked mails-agent MCP Server (mails0) into Claude Code and it worked on the first try. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out. Would recommend without hesitation.
Used for Keeping project tickets in sync with code changes
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Earned a permanent spot in my config
Replaced a homegrown script with mails-agent MCP Server (mails0) and have not looked back. You create a token and pass it in. Scope it narrowly, that is the main thing.
Used for Code review summaries for pull requests
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Decent, not set-and-forget
Took longer to configure than I expected. Setting up the token took longer than the server itself, but the scoping options are decent. Keeping it to local experiments for now.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Works, just lock it down
Some tools are great, a couple feel half finished. Release pace is moderate, so I pin a version and check in monthly. Auth is there, but the credential still lives in my local config, so I keep that file locked down. Local stdio process, easy to start and stop from the client. Keep permissions tight and it is a good tool.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Good defaults, good docs
Our agents call this dozens of times a day. The scope options are worth reading carefully, the defaults are broader than I wanted. It is in our production agent and I sleep fine.
Used for CI failure investigation
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.