Home / MCP registry index / io.github.cherami-mail/cherami-mcp

Cherami

io.github.cherami-mail/cherami-mcp in the official MCP registry. Endpoint https://cherami.to/mcp.

The registry describes it as: Email inboxes for recurring agent work. Read, search, reply, draft and organize correspondence.

Tools it advertises

get_service_info get_account list_inboxes create_inbox get_inbox get_receiving_policy get_sending_policy update_inbox list_messages count_messages get_message list_threads get_thread read_raw_message read_attachment create_draft list_drafts get_draft update_draft send_draft delete_draft send_message reply_message reply_all_message forward_message list_sent get_sent_message update_message_labels update_sent_message_labels list_labels bulk_update_message_labels bulk_update_sent_message_labels update_thread_labels get_outbound_quota delete_message delete_sent_message delete_thread delete_inbox list_trash restore_message restore_sent_message submit_feedback

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-cherami-mail-cherami-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-cherami-mail-cherami-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Email MCP servers