Is @atomicmail/mcp-modelcontextprotocol MCP safe to give an agent?

read onlyneeds cautionverifiedhealthy

A factual risk summary built from @atomicmail/mcp-modelcontextprotocol’s real tool surface, execution model, and verification history — not a vibe. Trust score 73/100.

01What it can do

Only read-style tools observed — no write/destructive tools.

3 tools observed

02Execution model

Runs locally over stdio — the server process executes on your machine with your user's privileges. Vet the source and package before granting access.

Installs via npx (`npx -y @atomicmail/mcp-modelcontextprotocol`) — it pulls and executes third-party code; pin versions and review the source.

03Permissions & auth

Read email · write

The write/destructive access this server can exercise, inferred from its verified tools.

04Verification

handshakepassed — tool surface is real

runsmetadata:passed · tools_list:passed · handshake:passed · metadata:passed · tools_list:passed · handshake:passed · metadata:passed · metadata:passed · tools_list:passed · handshake:passed

last_checked2026-08-16 23:02Z

sourcesnpm registry [p4]

Reduce the risk

Worried about handing an agent raw access? See governed agents in action — Apex gives your AI paced, capped, fully-logged hands with approval queues before anything runs.

Explore Apex →

See also: full server page · setup · alternatives