Home / MCP registry index / io.github.open-salesblink/cold-email-salesblink

SalesBlink Cold Email

io.github.open-salesblink/cold-email-salesblink in the official MCP registry. Endpoint https://mcp.salesblink.io/mcp. Source: github.com/open-salesblink/skill.

The registry describes it as: Cold email sequences, leads, templates, senders, inbox, and analytics via the SalesBlink API.

Connect it

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

claude mcp add --transport http cold-email-salesblink https://mcp.salesblink.io/mcp

{
  "mcpServers": {
    "cold-email-salesblink": {
      "url": "https://mcp.salesblink.io/mcp"
    }
  }
}

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

signup get_all_lists create_list get_list update_list get_all_templates create_template get_template update_template get_inbox_threads get_thread_messages send_reply forward_inbox_message update_mail_state get_all_sequences create_sequence get_sequence update_sequence get_sequence_stats get_all_users add_user get_user update_user generate_login_link get_all_senders get_all_folders add_contacts remove_contact get_sent_activity get_opens_activity get_clicks_activity get_replies_activity archive_list archive_template archive_sequence archive_contact get_leads update_lead move_lead get_all_workspaces create_workspace update_workspace clone_sequence get_inbox_placement_tests create_inbox_placement_test pause_inbox_placement_test delete_inbox_placement_test get_reports create_folder get_warmup_links get_sender_connect_link get_bulk_senders_upload_link initialize_google_oauth initialize_outlook_oauth get_custom_domains get_signatures get_api_keys get_api_key_page_link get_api_key_refresh_link delete_api_key and 28 more

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-10-31): a40ac1e7e792e8c9. 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.

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-open-salesblink-cold-email-salesblink/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-open-salesblink-cold-email-salesblink)

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 · Analytics and SEO MCP servers