Home / MCP registry index / io.usefulapi/mailshake

Mailshake MCP by usefulapi

io.usefulapi/mailshake in the official MCP registry. Endpoint https://mailshake.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read campaigns, replies and leads; pause or resume campaigns; close or reopen leads in Mailshake.

We read its 20 tools on 2026-11-02. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

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

Claude Code

claude mcp add --transport http mailshake https://mailshake.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "mailshake": {
      "url": "https://mailshake.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"mailshake","type":"http","url":"https://mailshake.usefulapi.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.

Install lazaretto-guard

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

Tools it advertises

mailshake_get_account mailshake_list_team_members mailshake_list_senders mailshake_list_campaigns mailshake_get_campaign mailshake_list_recipients mailshake_list_leads mailshake_list_sent_messages mailshake_list_replies mailshake_list_opens mailshake_list_clicks mailshake_list_created_leads mailshake_list_lead_status_changes mailshake_pause_campaign mailshake_unpause_campaign mailshake_pause_recipient mailshake_unpause_recipient mailshake_close_lead mailshake_ignore_lead mailshake_reopen_lead

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-02): 252e10e99e5a2831. 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:

Markdown

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

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.