emails (hasna/emails) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Emerging
74/100
19 days ago

emails

Local and self-hosted email management and automation for agents, with first-class operator-owned AWS support

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

hasna

Source: github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: EMAILS_CLIENT_ENV_SECRET, EMAILS_MCP_HTTP_TOKEN, EMAILS_SELF_HOSTED_API_KEY, EMAILS_SESSION_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretEMAILS_CLIENT_ENV_SECRET
configEMAILS_DB_PATH
configEMAILS_JSON_OUTPUT
🔐 secretEMAILS_MCP_HTTP_TOKEN"$(openssl rand -hex 32)" emails-mcp --http
configEMAILS_MODESelf-hosted clients must set =self_hosted,
🔐 secretEMAILS_SELF_HOSTED_API_KEY(in that precedence order). The service uses
configEMAILS_SELF_HOSTED_HTTP_MAX_RESPONSE_BYTES
configEMAILS_SELF_HOSTED_URL, and one bearer credential:
🔐 secretEMAILS_SESSION_TOKEN, EMAILS_IDP_TOKEN, or
configMCP_HTTP_PORTOverride port with , --port <n>, or --port=<n>
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

170/170 tools missing one or more hints — prepare_inbox (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_email_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_agent_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +167 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

116/121 tool handlers declare input schemas (96%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

111/121 tool handlers wrap calls in try/catch (92%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 1/170 tools referenced in tests (1%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

56 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/hasna-emails-1ksobw)](https://m8ven.ai/mcp/hasna-emails-1ksobw)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 34721360404500879e48dfc5e01326db7987a3c2
code hash: 78af43e4fd58bf88a123650a291a0498e21c08fa354e37762d393e20129192cd
verified: 8/8/2026, 7:25:30 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client