Mailcannon
REMOTE · WWW.THINKANDAUTOMATE.DEV · SCANNED SEP 27
AI-powered email outreach platform — send campaigns with deliverability tracking.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 34 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1078 tokens (~31/item across 34 items; 34 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_contact" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Mailcannon MCP server?
Mailcannon is a hosted endpoint at https://www.thinkandautomate.dev/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.thinkandautomate.dev
claude mcp add --transport http ainaluc-mailcannon 'https://www.thinkandautomate.dev/api/mcp'
{
"mcpServers": {
"ainaluc-mailcannon": {
"url": "https://www.thinkandautomate.dev/api/mcp"
}
}
} {
"servers": {
"ainaluc-mailcannon": {
"type": "http",
"url": "https://www.thinkandautomate.dev/api/mcp"
}
}
} [mcp_servers.ainaluc-mailcannon] url = "https://www.thinkandautomate.dev/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ainaluc-mailcannon": {
"type": "remote",
"url": "https://www.thinkandautomate.dev/api/mcp",
"enabled": true
}
}
} openclaw mcp add ainaluc-mailcannon --url 'https://www.thinkandautomate.dev/api/mcp' --transport streamable-http
mcp_servers:
ainaluc-mailcannon:
url: "https://www.thinkandautomate.dev/api/mcp" {
"McpServers": {
"ainaluc-mailcannon": {
"Transport": "http",
"Url": "https://www.thinkandautomate.dev/api/mcp"
}
}
} assistant mcp add ainaluc-mailcannon -t streamable-http -u 'https://www.thinkandautomate.dev/api/mcp'
{
"mcpServers": {
"ainaluc-mailcannon": {
"type": "http",
"url": "https://www.thinkandautomate.dev/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://www.thinkandautomate.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.thinkandautomate.dev | CN=YR1,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 6a1db5b50d00a2134e41cc27e9fed3bcead |
| SANs: www.thinkandautomate.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.thinkandautomate.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| thinkandautomate.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.thinkandautomate.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.thinkandautomate.dev/api/mcp | HTTPS enforced | 308 | https://www.thinkandautomate.dev/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_campaign_step ~54
Add a sequence step (delay in hours, subject, body)
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| campaignId | string | yes | – |
| day | number | yes | Delay in hours |
| subject | string | yes | – |
No output schema declared.
No examples provided.
add_contact ~57
Add a single contact
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| string | yes | – | |
| firstName | string | yes | – |
| lastName | string | – | – |
| tags | array | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
add_contacts ~23
Bulk add contacts (max 100)
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | – |
No output schema declared.
No examples provided.
add_provider ~62
Add an email provider
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | – |
| command | string | – | – |
| env | object | – | – |
| kind | string | yes | – |
| name | string | yes | – |
| transport | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
check_domain_deliverability ~43
Check SPF, DKIM, DMARC records for a domain
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check (e.g. thinkandautomate.dev) |
No output schema declared.
No examples provided.
check_email_spam_score ~34
Analyze email subject/body for spam trigger words
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| subject | string | yes | – |
No output schema declared.
No examples provided.
check_step_spam_score ~31
Check a campaign step's subject and body for spam triggers
| Name | Type | Req | Description |
|---|---|---|---|
| stepId | string | yes | – |
No output schema declared.
No examples provided.
create_campaign ~21
Create a new email campaign
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
create_task ~46
Create a new task
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| dueDate | string | – | ISO date (optional) |
| priority | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
delete_campaign ~23
Delete a campaign and all its steps
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
delete_campaign_step ~23
Delete a step from a campaign
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
delete_task ~21
Delete a task by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_deliverability ~24
Get deliverability stats (sent, opens, bounces, replies)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_setting ~25
Get a user setting (e.g. timezone)
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
No output schema declared.
No examples provided.
list_campaigns ~16
List all campaigns with their steps
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_contacts ~12
List all contacts
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_providers ~14
List all email providers
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_schedules ~15
List all scheduled campaign runs
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_settings ~13
List all user settings
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tags ~16
List all unique tags across your contacts
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tasks ~12
List all tasks
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pause_campaign ~28
Pause a campaign — stops processing all active schedules for this campaign
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
process_campaigns ~36
Process all due campaign schedules (includeFailed: true to retry failed ones)
| Name | Type | Req | Description |
|---|---|---|---|
| includeFailed | boolean | – | Also retry failed schedules |
No output schema declared.
No examples provided.
remove_contact ~21
Remove a contact by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
remove_provider ~21
Remove a provider by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
resume_campaign ~27
Resume a paused campaign — reactivates all paused schedules
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
retry_failed ~17
Reset all failed schedules to active for retry
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
schedule_campaign ~80
Assign contacts to a campaign and schedule it
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | – |
| contactIds | array | – | Contact IDs (ignored if tags provided) |
| providerId | string | – | Provider ID (optional) |
| startAt | string | – | ISO date (optional) |
| tags | array | – | Filter contacts by tag (overrides contactIds) |
No output schema declared.
No examples provided.
send_test_email ~49
Send a test email to yourself to preview formatting
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| providerId | string | – | Provider ID (optional, uses first available) |
| subject | string | yes | – |
No output schema declared.
No examples provided.
set_setting ~38
Set a user setting (e.g. timezone to 'America/New_York')
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| value | string | yes | – |
No output schema declared.
No examples provided.
update_campaign ~28
Update a campaign's name
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
update_campaign_step ~52
Update a campaign step's day, subject, or body
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| day | number | – | Delay in hours |
| id | string | yes | – |
| subject | string | – | – |
No output schema declared.
No examples provided.
update_contact_tags ~34
Set tags on a contact (replaces all tags)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| tags | array | yes | – |
No output schema declared.
No examples provided.
update_task ~62
Update a task's status, priority, or fields
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| dueDate | string | – | – |
| id | string | yes | – |
| priority | string | – | – |
| status | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
What is the Mailcannon MCP server?
Mailcannon is an MCP server listed in the public MCP registry as io.github.AinaLuc/mailcannon. AI-powered email outreach platform, send campaigns with deliverability tracking. This page covers its hosted endpoint (https://www.thinkandautomate.dev/api/mcp).
Is the Mailcannon MCP server safe to use?
Mailcannon scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mailcannon MCP server expose?
Mailcannon exposes 34 tools: add_contact, add_contacts, list_contacts, remove_contact, update_contact_tags, and 29 more. Their descriptions and schemas cost roughly 1,078 tokens of context every time the server is loaded.
Does the Mailcannon MCP server require authentication?
No. We connected to Mailcannon without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Mailcannon MCP server still maintained?
Mailcannon is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.