Home / MCP registry index / io.setip/emailmcp

EmailMCP

io.setip/emailmcp in the official MCP registry. Endpoint https://mcp.setip.io/mcp. Source: github.com/nfodor/emailmcp.

The registry describes it as: AI agent email — 23 tools free to read inbox, 28 paid to send. $9.99/mo. Token auto-provisioned.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http emailmcp https://mcp.setip.io/mcp

{
  "mcpServers": {
    "emailmcp": {
      "url": "https://mcp.setip.io/mcp"
    }
  }
}

code --add-mcp '{"name":"emailmcp","type":"http","url":"https://mcp.setip.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

send_email send_template_email validate_email get_email_usage verify_email_setup list_email_accounts read_inbox get_mailbox_status list_mailboxes start_smtp_receiver stop_smtp_receiver get_smtp_receiver_status get_forwarded_emails get_conversation_threads get_conversation_context get_threads_for_sender check_email_config configure_mailgun test_email_config create_mailbox delete_mailbox list_local_mailboxes request_email_ip check_ip_status get_dns_records verify_autonomous_setup setup_autonomous_security create_email_rule list_email_rules delete_email_rule update_email_rule start_idle_watch stop_idle_watch get_idle_status provision_start provision_resume provision_status list_cloud_providers start_health_monitor get_health_status add_sending_domain list_sending_domains remove_sending_domain get_domain_dns_records regenerate_zone_file create_email_account delete_email_account list_email_accounts_managed reset_account_password start_domain_verification stop_domain_verification get_domain_verification_status get_domain_verification_emails set_personal_email_credentials get_suppression_list remove_from_suppression

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-04): fb9c04c657fdacf9. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

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

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. How tool poisoning works. What we found across the registry. Check another server.

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