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 Studio

REMOTE · MCP.MOLTLINESTUDIO.COM

Fleet entry point: 22 hosted MCP servers, 160 tools, 110 free. Searches 138 agent skills.

0 this week 88 Trust /100

Last scanned (11 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Productivity and Notes

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
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2187 tokens (~218/item across 10 items; 10 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 25 Oct 26 0
    • Tool “get_free_skill” rewrote its description, which is the text the model reads security
    • Tool “get_full_kit” rewrote its description, which is the text the model reads security
    • Tool “get_full_persona” rewrote its description, which is the text the model reads security
    • Tool “get_full_product” rewrote its description, which is the text the model reads security
    • Tool “get_full_skill” rewrote its description, which is the text the model reads security
    • Tool “list_kits” rewrote its description, which is the text the model reads security
    • Tool “preview_product” rewrote its description, which is the text the model reads security
    • Tool “recommend_products” rewrote its description, which is the text the model reads security
    • Tool “search_catalog” rewrote its description, which is the text the model reads security
    • Tool “upgrade_info” rewrote its description, which is the text the model reads security
  • 13 Oct 26 +1
    • Stability: 0.97 → pass security
  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 97. That category is still filling its 30-day observation window: 27 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.

  • 9 Oct 26 +3

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

  • 3 Oct 26 +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.

  • 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
  • 14 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://mcp.moltlinestudio.com/catalog

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 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA256 5fcf21014c71aedb0ee8aa375beac0b4
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. DS published 19718 13 Verified
moltlinestudio.com. DS published 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' 'nonce-8e86650e-fec8-4ea5-84cc-0a38e51f06b1'; 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/catalog Verified 200
http (plaintext) http://mcp.moltlinestudio.com/catalog HTTPS enforced 301 https://mcp.moltlinestudio.com/catalog
MCP tools · 10 exposed · ~2,122 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
get_free_skill ~217

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

Structured output declared, but exposes no named fields.

No examples provided.

get_full_kit ~203

Load a themed kit and every member product in full. PREMIUM (paid plan). Typical input {"slug": "founder-kit"} returns {"slug": ..., "name": ..., "products": [{"slug": ..., "name": ..., "persona": ..., "skills": [...]}, ...]}. Returns every member product of one bundle in full, so the payload is large. Use only after list_kits has confirmed the kit slug. Not for a single product (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 kit '<value>'"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
slugstringyesKit slug exactly as returned by list_kits, e.g. "founder-kit".

Structured output declared, but exposes no named fields.

No examples provided.

get_full_persona ~183

Load a product's complete persona definition. PREMIUM (paid plan). Typical input {"slug": "inbox-zero-assistant"} returns {"slug": ..., "persona": "<full persona text>"}. Returns the persona text alone, with no skill bodies. Use when the caller needs the product's voice and operating rules only. Not when skills are also wanted - get_full_product returns persona and every skill in one call. 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 search_catalog.

Structured output declared, but exposes no named fields.

No examples provided.

get_full_product ~200

Load one product in full: persona plus every skill's instructions. PREMIUM (paid plan). Typical input {"slug": "inbox-zero-assistant"} returns {"slug": ..., "name": ..., "persona": ..., "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 bundle of products (get_full_kit). 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 search_catalog.

Structured output declared, but exposes no named fields.

No examples provided.

get_full_skill ~235

Load one paid skill's complete instructions from a product. PREMIUM (paid plan). Typical input {"slug": "inbox-zero-assistant", "skill_name": "Deep Triage"} returns {"slug": ..., "skill": ..., "instructions": "<full skill text>"}. Returns one named skill, selected by skill_name. Use after preview_product has shown the skill list and 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 shown in preview_product's "skills" list for that product.
slugstringyesProduct slug exactly as returned by search_catalog.

Structured output declared, but exposes no named fields.

No examples provided.

list_kits ~208

List the 12 themed kits with pricing and member products. FREE. Takes no arguments. Returns a list of kit objects, each {"slug": ..., "name": ..., "price_usd": N, "tagline": ..., "members": ["product-slug", ...], "availability": ...}. Use a kit's slug with get_full_kit (premium). Kits are not sold standalone on any marketplace: price_usd is the bundle's reference value, and All-Access is how a caller actually unlocks one. Use when the caller asks about bundles or bundle pricing. Not for individual products (search_catalog) and not for a kit's full contents (get_full_kit). 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.

preview_product ~235

Preview one product: metadata, persona teaser, and paid-skill teasers. FREE. Typical input {"slug": "inbox-zero-assistant"} returns {"slug": ..., "name": ..., "tagline": ..., "persona_preview": ..., "skills": [{"name": ..., "preview": ...}], "free_skill": ..., "note": ...}. Returns teasers only, never full text. Use to judge a product before committing. Not for the complete persona or skill bodies (get_full_persona, get_full_product), and not when the caller wants instructions they can act on now (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>"} (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 search_catalog or recommend_products, e.g. "inbox-zero-assistant".

Structured output declared, but exposes no named fields.

No examples provided.

recommend_products ~223

Recommend catalog products for a need described in plain language. FREE. Typical input {"need": "help answering customer support emails"} returns {"need": ..., "recommendations": [{"slug": ..., "name": ..., "why": ..., "area": ..., "try_free": "<free skill name>"}], "next": "..."}. Use when the caller describes a problem instead of naming a product; ranking is by fit to the described need. Not for exact keyword or slug lookups (search_catalog). 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
limitinteger–Maximum recommendations; values outside 1-10 are clamped. Default 5.
needstringyesThe job or problem in plain language, a few words or a sentence, e.g. "help answering customer support emails".

Structured output declared, but exposes no named fields.

No examples provided.

search_catalog ~274

Search all 138 catalog products by keyword and/or focus area. FREE. Typical input {"query": "email inbox", "limit": 5} returns a ranked list of product objects [{"slug": ..., "name": ..., "area": ..., "segment": ..., "tagline": ...}]. An empty query with an area set browses that area. Use when the caller names a keyword, product, or focus area to look up. Not for bundles (list_kits) and not for plain-language problem statements, which recommend_products ranks by fit rather than keyword match. 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
areastring–Optional focus-area filter; one of "productivity", "developertools", "personalassistant", "creative", "industryspecific", "educational". Empty means all areas.
limitinteger–Maximum results to return; values outside 1-100 are clamped. Default 15.
querystring–Space-separated keywords matched against name, tagline, slug, and segment, e.g. "email inbox".
NameTypeReqDescription
resultarrayyes–

No examples provided.

upgrade_info ~144

Explain how to unlock full personas, paid skills, and kits. FREE. Takes no arguments. Returns {"message": ..., "how": ..., "free_tier": ...} describing the upgrade path and what stays free. Use when a premium tool has been refused or the caller asks what a plan covers. Not for per-bundle or per-product pricing (list_kits, preview_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>"}. 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.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Moltline Studio MCP server?

Moltline Studio is a hosted endpoint at https://mcp.moltlinestudio.com/catalog, 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-catalog 'https://mcp.moltlinestudio.com/catalog'
Common questions

What is the Moltline Studio MCP server?

Moltline Studio is an MCP server listed in the public MCP registry as com.moltlinestudio/catalog. Fleet entry point: 22 hosted MCP servers, 160 tools, 110 free. Searches 138 agent skills. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/catalog).

Is the Moltline Studio MCP server safe to use?

Moltline Studio scores 88 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 Studio MCP server expose?

Moltline Studio exposes 10 tools: search_catalog, preview_product, get_free_skill, list_kits, upgrade_info, and 5 more. Their descriptions and schemas cost roughly 2,122 tokens of context every time the server is loaded.

Does the Moltline Studio MCP server require authentication?

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

Is the Moltline Studio MCP server still maintained?

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

What did VerifyMCP test on the Moltline Studio MCP server?

VerifyMCP ran 13 checks on Moltline Studio, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.