Moltline Outbound Engine
com.moltlinestudio/outboundVersion 1.2.07 outreach, sequencing, call-coaching and CRM-hygiene skill products. 6 of 8 free.
Status
Responds218 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:24 UTC
- Latency
- 218 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.moltlinestudio.com/outboundResponds218 msNo sign-in
Claude Code
claude mcp add --transport http outbound https://mcp.moltlinestudio.com/outboundClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: outbound
Remote MCP server URL: https://mcp.moltlinestudio.com/outboundCursor
{
"mcpServers": {
"outbound": {
"url": "https://mcp.moltlinestudio.com/outbound"
}
}
}VS Code
code --add-mcp '{"name":"outbound","type":"http","url":"https://mcp.moltlinestudio.com/outbound"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
8 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
audit_copyAudit 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. | No | Yes | Yes | No |
get_free_skillLoad a product's free gateway skill with its complete instructions. FREE.
Typical input {"slug": "linkedin-outreach-pro"} 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. | No | Yes | Yes | No |
get_full_productLoad one product in full: its persona plus every paid skill. PREMIUM (license).
Typical input {"slug": "linkedin-outreach-pro"} 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. | No | Yes | Yes | No |
get_full_skillLoad one paid skill's complete instructions from a product. PREMIUM (license).
Typical input {"slug": "linkedin-outreach-pro", "skill_name":
"outreach-sequence-writer"} 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. | No | Yes | Yes | No |
list_productsList the 7 outbound products with their included skills. FREE.
Takes no arguments. Returns a list of product objects, each {"slug":
"linkedin-outreach-pro", "name": ..., "tagline": ..., "skills":
["outreach-sequence-writer", ...], "free_skill": "connection-request-rewriter"}. 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. | No | Yes | Yes | No |
sequence_plannerPlan 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. | No | Yes | Yes | No |
subject_line_scorerScore 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. | No | Yes | Yes | No |
utm_builderBuild 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. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Sep 8, 2026
- Updated
- Sep 8, 2026
- Categories (suggested)
- CRMSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared