What are the risks of connecting to npm:clawaimail-mcp?

References sensitive file paths / environment secrets. Overall trust grade D (67/100).

When was npm:clawaimail-mcp last audited?

Last checked 2026-08-19; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

npm:clawaimail-mcp

Item: npm:clawaimail-mcp
Rating: 67
Author: wmcp.sh

https://www.npmjs.com/package/clawaimail-mcp

67/100 · MCP Trust Grade · checked 24d ago · MCP 0.2.0

Is the npm:clawaimail-mcp MCP server safe to use?

Independent trust grade D (67/100). References sensitive file paths / environment secrets. wmcp.sh continuously watches npm:clawaimail-mcp for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 9 tools · Productivity

list_inboxes

List all email inboxes

create_inbox

Create a new email inbox (optional — a default inbox is auto-created if needed)

send_email

Send an email. If inbox_id is omitted, uses the default inbox (auto-created if needed).

list_messages

List messages. If inbox_id is omitted, uses the default inbox.

read_email

Read a specific email message. If inbox_id is omitted, uses the default inbox.

search_emails

Search emails by keyword. If inbox_id is omitted, uses the default inbox.

delete_inbox

Delete an inbox and all its messages

account_info

Get account info, plan limits, and usage

my_email

Get your agent\

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 9 tool(s) detected in source

Security (OWASP MCP)30%25

⚠ references sensitive file paths / env secrets
scanned 1 source file

Maintenance / popularity20%75

last published ~5mo ago
3 published versions

Tool hygiene15%70

no TypeScript types
2 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
52 weekly downloads

Findings

WARNMCP08 References sensitive file paths / environment secrets.

INFO Static analysis of npm package clawaimail-mcp@0.2.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:clawaimail-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:clawaimail-mcp grade D

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Aclawaimail-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade D](https://wmcp.sh/mcp/grade/npm%3Aclawaimail-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Aclawaimail-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Aclawaimail-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3Aclawaimail-mcp/badge.svg" alt="MCP Trust Grade D · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.