io.github.Bluecraft-AI/machfive

REMOTE · MCP.MACHFIVE.IO · SCANNED AUG 3

Generate hyper-personalized cold email sequences via MachFive API.

Available components

+6 this week 76 76 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security74

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
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 Usability85

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 1027 tokens (~114/item across 9 items; 6 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.machfive.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http bluecraft-ai-machfive https://mcp.machfive.io/mcp

# ~/.codex/config.toml

[mcp_servers.bluecraft-ai-machfive]
url = "https://mcp.machfive.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bluecraft-ai-machfive": {
      "type": "remote",
      "url": "https://mcp.machfive.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add bluecraft-ai-machfive --url https://mcp.machfive.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  bluecraft-ai-machfive:
    url: "https://mcp.machfive.io/mcp"

// mcp.json

{
  "mcpServers": {
    "bluecraft-ai-machfive": {
      "type": "http",
      "url": "https://mcp.machfive.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 70

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Probed https://mcp.machfive.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=mcp.machfive.io	CN=YE2,O=Let's Encrypt,C=US	20 Jun 2026	18 Sept 2026	ECDSA 256	ECDSA-SHA384	518682aa40408415128c1b13b8a1a10626c
SANs: mcp.machfive.io
CN=YE2,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of mcp.machfive.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
machfive.io.	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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.machfive.io/mcp	Verified	200
http (plaintext)	http://mcp.machfive.io/mcp	HTTPS enforced	301	https://mcp.machfive.io/mcp

MCP tools — 6 exposed · ~924 tokens

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.

Tool Tokens

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.

Input Output Examples

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.

Input Output Examples

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":"[email protected]","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.

Input Output Examples

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.
email	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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	70
27 Jul	70
28 Jul	71
29 Jul	72
30 Jul	72
31 Jul	74
1 Aug	75
2 Aug	75
3 Aug	76