Home / MCP registry index / io.usefulapi/emailchef
Emailchef MCP by usefulapi
io.usefulapi/emailchef in the official MCP registry.
Endpoint https://emailchef.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read lists, contacts, campaign stats; add contacts; draft, schedule and send campaigns and SMS.
We read its 43 tools on 2026-11-01. 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 every week.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http emailchef https://emailchef.usefulapi.io/mcp{
"mcpServers": {
"emailchef": {
"url": "https://emailchef.usefulapi.io/mcp"
}
}
}code --add-mcp '{"name":"emailchef","type":"http","url":"https://emailchef.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.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
emailchef_get_account emailchef_get_subscription emailchef_list_senders emailchef_list_timezones emailchef_list_lists emailchef_get_list emailchef_get_list_stats emailchef_get_list_contact_counts emailchef_create_list emailchef_update_list emailchef_list_contacts emailchef_get_contact emailchef_create_contact emailchef_update_contact emailchef_unsubscribe_contact emailchef_import_contacts emailchef_list_import_tasks emailchef_get_import_task emailchef_list_predefined_fields emailchef_list_custom_fields emailchef_list_segments emailchef_get_segment emailchef_list_blocked emailchef_block_emails emailchef_unblock_email emailchef_get_campaign_counts emailchef_list_campaigns emailchef_get_campaign emailchef_get_campaign_links emailchef_list_campaign_engagement emailchef_create_campaign emailchef_clone_campaign emailchef_update_campaign emailchef_send_test_campaign emailchef_schedule_campaign emailchef_unschedule_campaign emailchef_send_campaign emailchef_archive_campaign emailchef_unarchive_campaign emailchef_send_email emailchef_get_sms_balance emailchef_get_sms_status emailchef_send_sms
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-01):
1789f9715dcd21ab. 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: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-emailchef)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.