# Moltline Outbound Engine (remote · mcp.moltlinestudio.com)

7 outreach, sequencing, call-coaching and CRM-hygiene skill products. 6 of 8 free.

- Trust score: 87/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.moltlinestudio.com`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-moltlinestudio-outbound/outbound.md), [page](https://verifymcp.io/servers/com-moltlinestudio-outbound/outbound)

## Channel facts

- Endpoint: `https://mcp.moltlinestudio.com/outbound`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1960 tokens (~245/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Moltline Outbound Engine MCP server?

Moltline Outbound Engine is a hosted endpoint at https://mcp.moltlinestudio.com/outbound, 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.

### Claude

```bash
claude mcp add --transport http com-moltlinestudio-outbound 'https://mcp.moltlinestudio.com/outbound'
```

### Cursor

```json
{
  "mcpServers": {
    "com-moltlinestudio-outbound": {
      "url": "https://mcp.moltlinestudio.com/outbound"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-moltlinestudio-outbound": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/outbound"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-moltlinestudio-outbound]
url = "https://mcp.moltlinestudio.com/outbound"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-moltlinestudio-outbound": {
      "type": "remote",
      "url": "https://mcp.moltlinestudio.com/outbound",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-moltlinestudio-outbound --url 'https://mcp.moltlinestudio.com/outbound' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-moltlinestudio-outbound:
    url: "https://mcp.moltlinestudio.com/outbound"
```

### Netclaw

```json
{
  "McpServers": {
    "com-moltlinestudio-outbound": {
      "Transport": "http",
      "Url": "https://mcp.moltlinestudio.com/outbound"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-moltlinestudio-outbound -t streamable-http -u 'https://mcp.moltlinestudio.com/outbound'
```

### Other

```json
{
  "mcpServers": {
    "com-moltlinestudio-outbound": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/outbound"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-16 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-09-15 (score 87, +1)

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

### 2026-09-13 (score 86, +1)

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

### 2026-09-11 (score 85, +1)

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

### 2026-09-09 (score 84, +1)

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

### 2026-09-06 (score 83, +1)

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

### 2026-09-04 (score 82, +1)

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

### 2026-09-02 (score 81, +1)

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

## MCP tools (8)

### `list_products` (~209 tokens)

List Products

List the 7 outbound products with their included skills. FREE.

Takes no arguments. Returns a list of product objects, each {"slug":
"linkedin-outreach", "name": ..., "tagline": ..., "skills": ["Skill
A", ...], "free_skill": "Gateway Skill Name"}. Use the returned slug
values with get_free_skill, get_full_product, or get_full_skill.

Returns metadata only - no persona text and no skill instructions. Use
when the caller wants to see what this server covers. Not for keyword
search across the whole 138-product catalog, which the catalog server's
search_catalog does, and not for instructions the caller can act on
(get_free_skill). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Output parameters:

- `result` (array)

### `get_free_skill` (~216 tokens)

Get Free Skill

Load a product's free gateway skill with its complete instructions. FREE.

Typical input {"slug": "linkedin-outreach"} returns {"slug": ...,
"skill": "<skill name>", "instructions": "<full skill text>"}.

Returns exactly one skill - the product's free gateway skill - chosen
automatically from the slug, with no plan required. Use when the caller
wants usable instructions immediately. Not for the product's other skills:
those are named and need get_full_skill with a skill_name, which requires
a paid plan. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown slug '<value>'. Use list_products."}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `slug` (string, required): Product slug exactly as returned by list_products, e.g. "linkedin-outreach".

### `audit_copy` (~222 tokens)

Audit Copy

Audit outreach copy for spam triggers and deliverability risks. FREE.

Checks spam-trigger phrases, length, structure, caps, links, and
personalization signals. Typical input {"subject": "Quick question",
"body": "<email text>"} returns {"score": 0-100, "findings":
["Spam-trigger phrases: ...", "Long for cold outreach (200 words; aim
50-125)"], "note": "..."}.

Use on the body of an outreach message. Not for the subject line alone
(subject_line_scorer) and not for the send schedule (sequence_planner). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `body` (string): The email body text to audit.
- `subject` (string): The email subject line; may be empty when auditing body copy alone.

### `get_full_product` (~218 tokens)

Get Full Product

Load one product in full: its persona plus every paid skill. PREMIUM (license).

Typical input {"slug": "linkedin-outreach"} returns {"slug": ...,
"name": ..., "persona": "<persona text>", "skills": [{"name": ...,
"instructions": ...}, ...], "free_skill": {...}}.

Returns persona plus every skill for one product. Use when the caller
wants the whole product. Not for a single skill (get_full_skill) and not
for a free look, which list_products and get_free_skill provide with no
plan. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown slug '<value>'"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `slug` (string, required): Product slug exactly as returned by list_products, e.g. "linkedin-outreach".

### `get_full_skill` (~223 tokens)

Get Full Skill

Load one paid skill's complete instructions from a product. PREMIUM (license).

Typical input {"slug": "linkedin-outreach", "skill_name": "Connection
Openers"} returns {"slug": ..., "skill": ..., "instructions": "<full
skill text>"}.

Returns one named skill, selected by skill_name. Use when the caller wants
one specific paid skill. Not for the free gateway skill, which
get_free_skill returns with no plan, and not for every skill at once
(get_full_product). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown slug '<value>'"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `skill_name` (string, required): Exact skill name as listed in that product's "skills" array from list_products.
- `slug` (string, required): Product slug exactly as returned by list_products.

### `sequence_planner` (~280 tokens)

Sequence Planner

Plan an outreach cadence with expanding gaps and per-touch purposes. FREE.

Spaces N touches across D days, alternating channels. Typical input
{"touches": 5, "days": 14, "channels": ["email", "linkedin"]} returns
{"days": 14, "plan": [{"touch": 1, "day": 0, "channel": "email",
"purpose": "open with a specific, researched reason"}, ...],
"rule": "..."}.

Use when cadence and per-touch purpose are the question. Not for the
wording of any single message (audit_copy). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `channels` (array): Channel names to alternate through in order, e.g. ["email", "linkedin", "phone"]. Default ["email", "linkedin"].
- `days` (integer): Total span of the sequence in days; values outside 1-365 are clamped. Default 14.
- `touches` (integer): Number of touches in the sequence; values outside 2-10 are clamped. Default 5.

### `subject_line_scorer` (~221 tokens)

Subject Line Scorer

Score and rank up to 20 email subject lines, best first. FREE.

Scores 0-100 on length, spam triggers, caps, personalization merge fields,
and curiosity cues. Typical input {"subjects": ["Quick question about
{{company}}", "ACT NOW!!!"]} returns {"ranked": [{"subject": ...,
"score": 92, "notes": ["personalized (+)", "question format"]}, ...]}.

Use when several subject lines need ranking against deliverability and
curiosity signals. Not for article headlines, which the creator server's
headline_analyzer ranks, and not for message bodies (audit_copy). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `subjects` (array, required): List of candidate subject lines as plain strings; only the first 20 are scored.

### `utm_builder` (~305 tokens)

Utm Builder

Build a UTM-tagged URL for campaign tracking. FREE.

Typical input {"url": "https://example.com/pricing", "source":
"newsletter", "medium": "email", "campaign": "spring-launch"} returns
{"tagged_url": "https://example.com/pricing?utm_source=newsletter&
utm_medium=email&utm_campaign=spring-launch"}.

Use to build one tagged tracking URL. Not for analyzing campaign results
and not for anything that belongs in the message body (audit_copy). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "url must start with http(s)://"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `campaign` (string, required): utm_campaign value — the campaign name, e.g. "spring-launch".
- `content` (string): Optional utm_content value for A/B variants.
- `medium` (string, required): utm_medium value — the channel, e.g. "email" or "cpc".
- `source` (string, required): utm_source value — where the traffic comes from, e.g. "newsletter".
- `term` (string): Optional utm_term value for paid keywords.
- `url` (string, required): Destination URL; must start with http:// or https://.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-moltlinestudio-outbound/outbound#diagnostics

## Score history

- 2026-09-20: 87
- 2026-09-19: 87
- 2026-09-18: 87
- 2026-09-17: 87
- 2026-09-16: 87
- 2026-09-15: 87
- 2026-09-14: 86
- 2026-09-13: 86
- 2026-09-12: 85
- 2026-09-11: 85
- 2026-09-10: 84
- 2026-09-09: 84
- 2026-09-08: 83
- 2026-09-07: 83
- 2026-09-06: 83
- 2026-09-05: 82
- 2026-09-04: 82
- 2026-09-03: 81
- 2026-09-02: 81
- 2026-09-01: 80
- 2026-08-31: 80
- 2026-08-30: 79
- 2026-08-29: 79
- 2026-08-28: 78
- 2026-08-27: 78
- 2026-08-26: 77
- 2026-08-25: 76
- 2026-08-24: 75
- 2026-08-23: 75
- 2026-08-22: 74

## Common questions

### What is the Moltline Outbound Engine MCP server?

Moltline Outbound Engine is an MCP server listed in the public MCP registry as com.moltlinestudio/outbound. 7 outreach, sequencing, call-coaching and CRM-hygiene skill products. 6 of 8 free. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/outbound).

### Is the Moltline Outbound Engine MCP server safe to use?

Moltline Outbound Engine scores 87 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 Moltline Outbound Engine MCP server expose?

Moltline Outbound Engine exposes 8 tools: list_products, get_free_skill, audit_copy, get_full_product, get_full_skill, and 3 more. Their descriptions and schemas cost roughly 1,894 tokens of context every time the server is loaded.

### Does the Moltline Outbound Engine MCP server require authentication?

No. We connected to Moltline Outbound Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Moltline Outbound Engine MCP server still maintained?

Moltline Outbound Engine is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.moltlinestudio.com/outbound
- Repository: https://github.com/GarphenGate/moltline-mcp
- Website: https://moltlinestudio.com/servers.html#outbound
- Changelog RSS feed: https://verifymcp.io/servers/com-moltlinestudio-outbound/outbound.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-moltlinestudio-outbound/outbound.json
- HTML version of this page: https://verifymcp.io/servers/com-moltlinestudio-outbound/outbound