Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.joansongjr/clawaimail

NPM · CLAWAIMAIL-MCP · SCANNED SEP 20

Email infrastructure for AI agents. Create inboxes, send/receive email, and search messages.

Available components

0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 286 tokens (~35/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_email" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.joansongjr/clawaimail MCP server?

io.github.joansongjr/clawaimail runs locally as an npm package, launched with npx -y clawaimail-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · clawaimail-mcp

# add to Claude Code
claude mcp add joansongjr-clawaimail -- npx -y clawaimail-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "joansongjr-clawaimail": {
      "command": "npx",
      "args": [
        "-y",
        "clawaimail-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "joansongjr-clawaimail": {
      "command": "npx",
      "args": [
        "-y",
        "clawaimail-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add joansongjr-clawaimail -- npx -y clawaimail-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "joansongjr-clawaimail": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "clawaimail-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add joansongjr-clawaimail --command npx --arg -y --arg clawaimail-mcp
# ~/.hermes/config.yaml
mcp_servers:
  joansongjr-clawaimail:
    command: "npx"
    args: ["-y", "clawaimail-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "joansongjr-clawaimail": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "clawaimail-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add joansongjr-clawaimail -t stdio -c npx -a -y clawaimail-mcp
// mcp.json
{
  "mcpServers": {
    "joansongjr-clawaimail": {
      "command": "npx",
      "args": [
        "-y",
        "clawaimail-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 13 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −2
    • Stability: pass → 0.80 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/clawaimail-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~286 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
account_info ~18

Get account info, plan limits, and usage

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

create_inbox ~41

Create a new email inbox

NameTypeReqDescription
usernamestringyesEmail username (e.g. "mybot" creates mybot@clawaimail.com)

No output schema declared.

No examples provided.

delete_inbox ~29

Delete an inbox and all its messages

NameTypeReqDescription
inbox_idnumberyesInbox ID to delete

No output schema declared.

No examples provided.

list_inboxes ~15

List all email inboxes

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_messages ~50

List messages in an inbox

NameTypeReqDescription
inbox_idnumberyesInbox ID
limitnumberMax messages to return (default 20)
unreadbooleanOnly show unread messages

No output schema declared.

No examples provided.

read_email ~34

Read a specific email message

NameTypeReqDescription
inbox_idnumberyesInbox ID
message_idnumberyesMessage ID

No output schema declared.

No examples provided.

search_emails ~33

Search emails by keyword

NameTypeReqDescription
inbox_idnumberyesInbox ID
querystringyesSearch query

No output schema declared.

No examples provided.

send_email ~66

Send an email from an inbox

NameTypeReqDescription
htmlstringHTML body
inbox_idnumberyesInbox ID to send from
subjectstringyesEmail subject
textstringPlain text body
tostringyesRecipient email address

No output schema declared.

No examples provided.

Common questions

What is the io.github.joansongjr/clawaimail MCP server?

io.github.joansongjr/clawaimail is an MCP server listed in the public MCP registry as io.github.joansongjr/clawaimail. Email infrastructure for AI agents. Create inboxes, send/receive email, and search messages. This page covers its npm package (clawaimail-mcp).

Is the io.github.joansongjr/clawaimail MCP server safe to use?

io.github.joansongjr/clawaimail scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.joansongjr/clawaimail MCP server expose?

io.github.joansongjr/clawaimail exposes 8 tools: list_inboxes, create_inbox, send_email, list_messages, read_email, and 3 more. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.

Is the io.github.joansongjr/clawaimail MCP server still maintained?

io.github.joansongjr/clawaimail is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.joansongjr/clawaimail MCP server under?

io.github.joansongjr/clawaimail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.