Moltline Studio
REMOTE · MCP.MOLTLINESTUDIO.COM · SCANNED SEP 21
Fleet entry point: 22 hosted MCP servers, 160 tools, 110 free. Searches 138 agent skills.
Available components
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. 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
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 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
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
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
claude mcp add --transport http com-moltlinestudio-catalog 'https://mcp.moltlinestudio.com/catalog'
{
"mcpServers": {
"com-moltlinestudio-catalog": {
"url": "https://mcp.moltlinestudio.com/catalog"
}
}
} {
"servers": {
"com-moltlinestudio-catalog": {
"type": "http",
"url": "https://mcp.moltlinestudio.com/catalog"
}
}
} [mcp_servers.com-moltlinestudio-catalog] url = "https://mcp.moltlinestudio.com/catalog"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-moltlinestudio-catalog": {
"type": "remote",
"url": "https://mcp.moltlinestudio.com/catalog",
"enabled": true
}
}
} openclaw mcp add com-moltlinestudio-catalog --url 'https://mcp.moltlinestudio.com/catalog' --transport streamable-http
mcp_servers:
com-moltlinestudio-catalog:
url: "https://mcp.moltlinestudio.com/catalog" {
"McpServers": {
"com-moltlinestudio-catalog": {
"Transport": "http",
"Url": "https://mcp.moltlinestudio.com/catalog"
}
}
} assistant mcp add com-moltlinestudio-catalog -t streamable-http -u 'https://mcp.moltlinestudio.com/catalog'
{
"mcpServers": {
"com-moltlinestudio-catalog": {
"type": "http",
"url": "https://mcp.moltlinestudio.com/catalog"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 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.
- 14 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Sept 26 74
First indexed and scored.
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 21 Sept 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 | 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/catalog | Verified | 200 | |
| http (plaintext) | http://mcp.moltlinestudio.com/catalog | HTTPS enforced | 301 | https://mcp.moltlinestudio.com/catalog |
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 →
get_free_skill 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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Product 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Kit 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Product slug exactly as returned by search_catalog. |
Structured output declared, but exposes no named fields.
No examples provided.
get_full_product 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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Product slug exactly as returned by search_catalog. |
Structured output declared, but exposes no named fields.
No examples provided.
get_full_skill 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.
| Name | Type | Req | Description |
|---|---|---|---|
| skill_name | string | yes | Exact skill name as shown in preview_product's "skills" list for that product. |
| slug | string | yes | Product slug exactly as returned by search_catalog. |
Structured output declared, but exposes no named fields.
No examples provided.
list_kits 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.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
preview_product 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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Product 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum recommendations; values outside 1-10 are clamped. Default 5. |
| need | string | yes | The 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Optional focus-area filter; one of "productivity", "developertools", "personalassistant", "creative", "industryspecific", "educational". Empty means all areas. |
| limit | integer | – | Maximum results to return; values outside 1-100 are clamped. Default 15. |
| query | string | – | Space-separated keywords matched against name, tagline, slug, and segment, e.g. "email inbox". |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
upgrade_info 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.
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 77 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.