Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Moltline Personal Suite

REMOTE · MCP.MOLTLINESTUDIO.COM · SCANNED SEP 20

20 inbox, calendar, travel, meals and family-logistics skill products. 7 of 9 free.

+1 this week 87 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2212 tokens (~245/item across 9 items; 9 tools + 0 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Moltline Personal Suite MCP server?

Moltline Personal Suite is a hosted endpoint at https://mcp.moltlinestudio.com/personal, 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.moltlinestudio.com

# add to Claude Code
claude mcp add --transport http com-moltlinestudio-personal 'https://mcp.moltlinestudio.com/personal'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-moltlinestudio-personal": {
      "url": "https://mcp.moltlinestudio.com/personal"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-moltlinestudio-personal": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/personal"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-moltlinestudio-personal]
url = "https://mcp.moltlinestudio.com/personal"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-moltlinestudio-personal": {
      "type": "remote",
      "url": "https://mcp.moltlinestudio.com/personal",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-moltlinestudio-personal --url 'https://mcp.moltlinestudio.com/personal' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-moltlinestudio-personal:
    url: "https://mcp.moltlinestudio.com/personal"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-moltlinestudio-personal": {
      "Transport": "http",
      "Url": "https://mcp.moltlinestudio.com/personal"
    }
  }
}
# add to Vellum
assistant mcp add com-moltlinestudio-personal -t streamable-http -u 'https://mcp.moltlinestudio.com/personal'
// mcp.json
{
  "mcpServers": {
    "com-moltlinestudio-personal": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/personal"
    }
  }
}

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.

  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +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.

  • 11 Sept 26 +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.

  • 9 Sept 26 +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.

  • 7 Sept 26 +1

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

  • 5 Sept 26 +1

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

  • 3 Sept 26 +1

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

  • 1 Sept 26 +1

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

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 20 Sept 2026 · Probed https://mcp.moltlinestudio.com/personal

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=moltlinestudio.com CN=WE1,O=Google Trust Services,C=US 15 Aug 2026 13 Nov 2026 ECDSA 256 ECDSA-SHA256 72e09c6114448e7a0ed370fb03c277cb
SANs: moltlinestudio.com, *.moltlinestudio.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.moltlinestudio.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
moltlinestudio.com. present 2371 13 Verified
mcp.moltlinestudio.com. Verified address RRset verified with the apex keys
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=15576000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.moltlinestudio.com https://mcp.moltlinestudio.com; form-action 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.moltlinestudio.com/personal Verified 200
http (plaintext) http://mcp.moltlinestudio.com/personal HTTPS enforced 301 https://mcp.moltlinestudio.com/personal
MCP tools · 9 exposed · ~2,145 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. 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 →

Tool Tokens
budget_split ~262

Split monthly income into needs/wants/savings buckets with weekly equivalents. FREE. Defaults to the 50/30/20 rule, fully customizable. Typical input {"monthly_income": 4000} returns {"needs": {"pct": 50, "monthly": 2000.0, "weekly": 461.54}, "wants": {...}, "savings": {...}, "note": "..."}. Use when monthly income needs allocating across buckets. Not for how long a target takes to reach (savings_goal). 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": "monthly_income must be > 0"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
monthly_incomenumberyesTake-home monthly income; must be greater than 0.
needs_pctnumberPercentage for needs; all three percentages must sum to 100. Default 50.
savings_pctnumberPercentage for savings. Default 20.
wants_pctnumberPercentage for wants. Default 30.

Structured output declared, but exposes no named fields.

No examples provided.

countdown_days ~244

Count the days until each named event, soonest first. FREE. Typical input {"events": {"Launch": "2026-10-01", "Trip": "2026-09-05"}} returns {"today": "YYYY-MM-DD", "events": [{"event": "Trip", "date": "2026-09-05", "days_away": 20}, ...]}; a bad date gets a per-event error entry instead of failing the whole call. Use to rank named dates by how soon they arrive. Not for working-day math, which the timeops server's business_days handles, and not for building a review schedule (spaced_repetition_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>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
eventsobjectyesMapping of event name to ISO date YYYY-MM-DD, e.g. {"Launch": "2026-10-01"}. The first 30 events are used.

Structured output declared, but exposes no named fields.

No examples provided.

get_free_skill ~218

Load a product's free gateway skill with its complete instructions. FREE. Typical input {"slug": "inbox-assistant"} 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.

NameTypeReqDescription
slugstringyesProduct slug exactly as returned by list_products, e.g. "inbox-assistant".

Structured output declared, but exposes no named fields.

No examples provided.

get_full_product ~220

Load one product in full: its persona plus every paid skill. PREMIUM (license). Typical input {"slug": "inbox-assistant"} 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.

NameTypeReqDescription
slugstringyesProduct slug exactly as returned by list_products, e.g. "inbox-assistant".

Structured output declared, but exposes no named fields.

No examples provided.

get_full_skill ~222

Load one paid skill's complete instructions from a product. PREMIUM (license). Typical input {"slug": "inbox-assistant", "skill_name": "Zero Sweep"} 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.

NameTypeReqDescription
skill_namestringyesExact skill name as listed in that product's "skills" array from list_products.
slugstringyesProduct slug exactly as returned by list_products.

Structured output declared, but exposes no named fields.

No examples provided.

list_products ~212

List every product in the Personal Suite line with its included skills. FREE. Takes no arguments. Returns a list of 20 product objects, each {"slug": "inbox-assistant", "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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

savings_goal ~281

Compute months to reach a savings target at a monthly contribution. FREE. Optionally compounds interest monthly. Administrative math only — not financial advice. Typical input {"target": 10000, "monthly_saving": 400, "annual_rate_pct": 4} returns {"months": 24, "years": 2.0, "final_balance": 10021.94, "interest_earned": 421.94, "note": "..."}. Use when a target amount and a monthly contribution are known. Not for allocating income across categories (budget_split) and not for loan repayment, which the business server's loan_payment computes. 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": "target and monthly_saving must be > 0"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
annual_rate_pctnumberAnnual interest rate percentage, 0 to 100, compounded monthly. Default 0.
monthly_savingnumberyesContribution per month; must be greater than 0.
targetnumberyesThe savings goal; must be greater than 0.

Structured output declared, but exposes no named fields.

No examples provided.

spaced_repetition_plan ~257

Build a spaced-repetition review schedule with expanding intervals. FREE. Intervals follow 1, 3, 7, 14, 30, 60, 120, 240 days. Typical input {"start_date": "2026-09-01", "sessions": 4} returns {"start": "2026-09-01", "reviews": [{"session": 1, "day_offset": 1, "date": "2026-09-02"}, ...]}. Use when material must be reviewed on expanding intervals. Not for timing a single session, which the educator server's lesson_timer handles. 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": "start_date must be YYYY-MM-DD"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
sessionsintegerNumber of review sessions; values outside 1-8 are clamped. Default 6.
start_datestringyesThe day you learned the material, ISO YYYY-MM-DD.

Structured output declared, but exposes no named fields.

No examples provided.

tip_split ~229

Compute the tip and per-person split for a bill. FREE. Typical input {"bill": 86.40, "tip_pct": 20, "people": 4} returns {"tip": 17.28, "total": 103.68, "per_person": 25.92}. Use for one bill shared among a group. Not for recurring household budgeting (budget_split). 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": "bill must be > 0 and people >= 1"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
billnumberyesThe pre-tip bill amount; must be greater than 0.
peopleintegerHow many people split the total; at least 1. Default 1.
tip_pctnumberTip percentage, 0 to 100. Default 18.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Moltline Personal Suite MCP server?

Moltline Personal Suite is an MCP server listed in the public MCP registry as com.moltlinestudio/personal. 20 inbox, calendar, travel, meals and family-logistics skill products. 7 of 9 free. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/personal).

Is the Moltline Personal Suite MCP server safe to use?

Moltline Personal Suite 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 Personal Suite MCP server expose?

Moltline Personal Suite exposes 9 tools: list_products, get_free_skill, budget_split, spaced_repetition_plan, get_full_product, and 4 more. Their descriptions and schemas cost roughly 2,145 tokens of context every time the server is loaded.

Does the Moltline Personal Suite MCP server require authentication?

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

Is the Moltline Personal Suite MCP server still maintained?

Moltline Personal Suite 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.