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.

studio.dodraft/getdeck

REMOTE · GETDECK.CO · SCANNED SEP 28

160+ finished slide layouts and 41 themes your agent can search, fetch and build a deck from

Available components

67 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 Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1004 tokens (~143/item across 7 items; 7 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 56% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the studio.dodraft/getdeck MCP server?

studio.dodraft/getdeck is a hosted endpoint at https://getdeck.co/api/mcp, 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 · getdeck.co

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

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.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

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

  • 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
  • 24 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 23 Sept 26 64

    First indexed and scored.

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 28 Sept 2026 · Probed https://getdeck.co/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=getdeck.co CN=YR1,O=Let's Encrypt,C=US 22 Sept 2026 21 Dec 2026 RSA 2048 SHA256-RSA 6e9a0170f332f0b39777b9283fc669791d6
SANs: getdeck.co
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of getdeck.co. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
getdeck.co. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://getdeck.co/api/mcp Verified 200
http (plaintext) http://getdeck.co/api/mcp HTTPS enforced 308 https://getdeck.co/api/mcp
MCP tools · 7 exposed · ~1,004 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
export_pptx ~136

Turn a deck into a downloadable .pptx file. Requests like "make it a PowerPoint", "PPT로 뽑아줘", or "export this deck" mean this tool. Takes the layout ids and the text for each slot, and returns a signed download link. Coordinates come from our measurements, so the file matches what the gallery shows — but the boxes are fixed, so text longer than slots[].max_chars will be clipped.

NameTypeReqDescription
slidesarrayyesUp to 25 slides, in order.
themestring–Theme id. Only measured themes work; omit to use the default.

No output schema declared.

No examples provided.

get_layout ~89

Return one layout as a ready-to-use, self-contained document: HTML, theme CSS, and its slot definitions. Call this once the user knows which layout they want, or with ids returned by suggest_deck.

NameTypeReqDescription
idstringyes–
langstring–Language for slot hints and usage notes. Pass the language the user is writing in.
theme_idstring––

No output schema declared.

No examples provided.

get_starter_kit ~69

Call this when joining several fetched layouts into one deck file. Requests like "merge these into one file", "bundle it as a deck", or "make it one HTML" mean this tool. Returns the base CSS, assembly rules, spacing tokens, and a viewport snippet for standalone viewing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_theme ~28

Return one theme in full: its complete CSS and design tokens.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

list_layouts ~151

Search or filter the layout catalog to find a specific layout. Returns metadata only, no HTML. Also the tool for "what is new", "any new layouts?", "what got added since last month" - pass `since` and it returns only what landed after that date. If the user asked for a whole deck rather than one slide, call suggest_deck first instead of this.

NameTypeReqDescription
categorystring––
limitinteger––
querystring––
sincestring–ISO date (YYYY-MM-DD). Only layouts added after it. Use for "what is new" questions; if the user gave no date, a month back is a sensible default.

No output schema declared.

No examples provided.

list_themes ~42

Search or filter the theme catalog. Returns metadata and key colors only, not the full CSS.

NameTypeReqDescription
moodstring––
schemestring––

No output schema declared.

No examples provided.

suggest_deck ~489

Compose a deck and return a preview link the user can open in the browser right away. The user sees what the finished deck looks like without a single file being generated. Use this for requests like "make me a pitch deck", "I need a sales deck", "10 slides for an investor update", "put together a product overview", or "show me a deck outline" - anything where the user has a topic but has not picked layouts yet. ALSO use it when the user already has layouts in hand - "이 레이아웃들 모아서 프리뷰 만들어줘", "combine these layouts into a preview", "추천 프리뷰 만들어줘", "show these together as a deck" - pass them as layout_ids and it returns ONE deck preview link for the whole set. Never answer that kind of request with a list of individual layout links: one deck preview is the deliverable. Returns one theme + a slide order + the preview link, plus a `clarify` question to put to the user so the composition and theme are their call, not a guess. Always pass the preview link through to the user verbatim, ask clarify.question with its options, and wait for the answer - then call this tool again with deck_id / theme_id as clarify.answer_with says. Do not start generating files while a clarify question is unanswered. Once it is settled, fetch each layout id with get_layout, then call get_starter_kit to join them into one deck.

NameTypeReqDescription
deck_idstring–The composition the user picked from a previous call's clarify.options. Skips topic matching.
layout_idsarray–Layout ids the user or you already picked, in slide order. Skips topic matching and slide_count: the preview link is built from exactly these layouts.
purposestringyesThe user's topic or goal, in their own words. e.g. "startup pitch deck", "quarterly business review"
slide_countinteger–How many slides. If the user did not say, use the default of 10 rather than asking.
theme_idstring–The theme the user picked from a previous call's clarify.options. Pass deck_id along with it.
tonestring–Desired mood. e.g. "minimal", "bold", "warm". Omit if the user did not mention one.

No output schema declared.

No examples provided.

Common questions

What is the studio.dodraft/getdeck MCP server?

studio.dodraft/getdeck is an MCP server listed in the public MCP registry as studio.dodraft/getdeck. 160+ finished slide layouts and 41 themes your agent can search, fetch and build a deck from. This page covers its hosted endpoint (https://getdeck.co/api/mcp).

Is the studio.dodraft/getdeck MCP server safe to use?

studio.dodraft/getdeck scores 67 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 studio.dodraft/getdeck MCP server expose?

studio.dodraft/getdeck exposes 7 tools: list_layouts, list_themes, get_layout, get_theme, get_starter_kit, and 2 more. Their descriptions and schemas cost roughly 1,004 tokens of context every time the server is loaded.

Does the studio.dodraft/getdeck MCP server require authentication?

No. We connected to studio.dodraft/getdeck without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the studio.dodraft/getdeck MCP server still maintained?

studio.dodraft/getdeck is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.