io.github.Bluecraft-AI/cold-email
REMOTE · MCP.MACHFIVE.IO
Generate hyper-personalized cold email sequences via AI.
Available components
Last scanned (12 hours ago)
Scores higher than 0% of remote servers
Reachable. Last reached 27 Sep 2026.
Category Marketing and SEO
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 Security0
- TLS not yet verified: the listed URL is a template whose api_key variable has no value or default, so there was no address for us to check.Unverified
- Authorisation not yet verified: the listed URL is a template whose api_key variable has no value or default, so there was no address for us to check.Unverified
- HTTPS not yet verified: the listed URL is a template whose api_key variable has no value or default, so there was no address for us to check. View diagnostics → Unverified
- HSTS not yet verified: the listed URL is a template whose api_key variable has no value or default, so there was no address for us to check.Unverified
- DNSSEC not yet verified: the listed URL is a template whose api_key variable has no value or default, so there was no address for us to check.Unverified
Transport & Reachability0
- Transport not yet verified: the listed URL is a template whose api_key variable has no value or default, so there is no address for us to connect to. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 7 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 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
- 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
- 9 Sept 26 0
- Schema quality: good → excellent 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability 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
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 5 Nov 2026 · Probed https://mcp.machfive.io/mcp/{api_key}
Transports 1 probe
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| http (plaintext) | http://mcp.machfive.io/mcp/%7Bapi_key%7D | Inconclusive |
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 →
export_list Export List ~90
Download the generated email sequences for a COMPLETED list. Only call this AFTER get_list_status shows processing_status = 'completed'. If the list is not yet completed, you'll get a 409 error — poll first.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format: 'json' (structured data) or 'csv' (raw CSV for sending tools). |
| list_id | string | yes | List UUID to export. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_batch Generate Batch ~236
Submit multiple leads for batch email sequence generation (ASYNC). Returns IMMEDIATELY with a list_id. Processing runs in the background. After calling this, poll get_list_status every 15-30 seconds until processing_status is 'completed' or 'failed', then call export_list. You must have a campaign_id first. Call list_campaigns if you don't have one.
| Name | Type | Req | Description |
|---|---|---|---|
| approved_ctas | string | – | Comma-separated CTAs. Omit to use campaign defaults. |
| campaign_angle | string | – | Additional context/angle for personalization. |
| campaign_id | string | yes | Campaign UUID from list_campaigns. |
| email_count | integer | – | Number of emails per lead, 1-5. |
| email_signature | string | – | Signature appended to each email. |
| leads_json | string | yes | JSON array of lead objects. Each MUST have "email". Optional: name, title, company, company_website, linkedin_url. Example: '[{"email":"jane@acme.com","name":"Jane Doe"}]' |
| list_name | string | – | Display name for this batch in MachFive UI. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_sequence Generate Email Sequence ~302
Generate a personalized cold email sequence for ONE lead. This is SYNCHRONOUS — the request takes 3-10 minutes because MachFive researches the prospect and crafts unique emails. Do NOT retry if it seems slow; wait for the response. You must have a campaign_id first. Call list_campaigns if you don't have one. If the request times out, use the returned list_id with get_list_status and export_list to recover results.
| Name | Type | Req | Description |
|---|---|---|---|
| approved_ctas | string | – | Comma-separated CTAs, e.g. 'Direct Meeting CTA, Lead Magnet CTA'. Omit to use campaign defaults. |
| campaign_angle | string | – | Additional context/angle for personalization. |
| campaign_id | string | yes | Campaign UUID from list_campaigns. |
| company | string | – | Lead's company name (improves personalization). |
| company_website | string | – | Company URL for AI research. |
| string | yes | Lead's email address (REQUIRED). | |
| email_count | integer | – | Number of emails in sequence, 1-5. |
| email_signature | string | – | Signature appended to each email. |
| linkedin_url | string | – | LinkedIn profile URL for deeper personalization. |
| list_name | string | – | Display name for this list in MachFive UI. |
| name | string | – | Lead's full name (improves personalization). |
| title | string | – | Lead's job title (improves personalization). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_list_status Get List Status ~79
Check the processing status of a lead list. Use this to POLL after calling generate_batch. Call every 15-30 seconds until processing_status is 'completed' or 'failed'. When completed, call export_list. When failed, submit a new batch.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | List UUID from generate_batch or generate_sequence response. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_campaigns List Campaigns ~108
List campaigns in the user's MachFive workspace. CALL THIS FIRST before generate_sequence or generate_batch — you need a campaign ID to generate emails. If the user hasn't specified a campaign, call this and ask them to pick one. Returns JSON array of campaigns with id, name, and created_at. Use the 'id' field as campaign_id in generate calls.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Search string to filter campaigns by name (case-insensitive substring match). Leave empty to list all. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_lists List Lead Lists ~109
List lead lists (batch jobs) in the user's MachFive workspace. Useful for browsing past batches, checking what's in progress, or finding a list_id to export. Results are ordered newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | – | Filter by campaign UUID. |
| limit | integer | – | Max results to return, 1-100. |
| offset | integer | – | Pagination offset. |
| status | string | – | Filter by processing status: 'pending', 'processing', 'completed', or 'failed'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.Bluecraft-AI/cold-email MCP server?
io.github.Bluecraft-AI/cold-email is a hosted endpoint at https://mcp.machfive.io/mcp/%7Bapi_key%7D, 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 · mcp.machfive.io
claude mcp add --transport http bluecraft-ai-cold-email 'https://mcp.machfive.io/mcp/%7Bapi_key%7D'
What is the io.github.Bluecraft-AI/cold-email MCP server?
io.github.Bluecraft-AI/cold-email is an MCP server listed in the public MCP registry as io.github.Bluecraft-AI/cold-email. Generate hyper-personalized cold email sequences via AI. This page covers its hosted endpoint (https://mcp.machfive.io/mcp/{api_key}).
Is the io.github.Bluecraft-AI/cold-email MCP server safe to use?
io.github.Bluecraft-AI/cold-email scores 0 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 io.github.Bluecraft-AI/cold-email MCP server expose?
io.github.Bluecraft-AI/cold-email exposes 6 tools: list_campaigns, generate_sequence, generate_batch, list_lists, get_list_status, export_list. Their descriptions and schemas cost roughly 924 tokens of context every time the server is loaded.
Does the io.github.Bluecraft-AI/cold-email MCP server require authentication?
Its publisher declares no required credentials for io.github.Bluecraft-AI/cold-email. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.Bluecraft-AI/cold-email MCP server still maintained?
io.github.Bluecraft-AI/cold-email 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.