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.

slide-deck.io

REMOTE · SLIDE-DECK.IO

Public remixable decks from a topic. Control.io product of Morton Technology Consulting, LLC.

Available components

0 this week 86 Trust /100

Last scanned (4 minutes ago)

Scores higher than 93% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Documents and Files

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 Security89
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 392 tokens (~130/item across 3 items; 3 tools + 0 resources), lean.Pass
  • 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 Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 37% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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 Oct 26 +2
    • Tool “populate_template” rewrote its description, which is the text the model reads security
    • Schema quality: 73 → 130 ▼ functional
    • Tool coverage: 13% → 37% ▲ functional
    • Schema quality: fair → good functional
    • “generate_report” added an optional parameter “csv” cosmetic
    • “generate_report” added an optional parameter “title” cosmetic
    • “populate_template” added an optional parameter “csv” cosmetic
    • “populate_template” added an optional parameter “title” cosmetic
    • “generate_report” reworded the description of “source” cosmetic
    • “populate_template” reworded the description of “source” cosmetic
  • 14 Oct 26 0
    • “generate_report” reworded the description of “source” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 1 Oct 26 0
    • Stability: 0.97 → pass security
  • 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
  • 22 Sept 26 0
    • Stability: fail → 0.70 functional
  • 1 Sept 26 0
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “generate_deck” was removed ▼ security
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 100% → 13% ▼ functional
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: behind authorisation → reachable ▲ functional
    • Schema quality: 191 → 74 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Destructive annotations: pass functional
    • Schema quality: excellent → fair functional
    • New tool “generate_report” functional
    • New tool “list_connectors” functional
    • New tool “populate_template” functional
  • 26 Aug 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
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://slide-deck.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=slide-deck.io CN=WE1,O=Google Trust Services,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 e2bbca35094c60980e35b3d1a6826a8d
SANs: slide-deck.io, *.slide-deck.io
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 insecure

Validation of slide-deck.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
slide-deck.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://static.cloudflareinsights.com https://us-assets.i.posthog.com https://www.googletagmanager.com; script-src-attr 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://r2.slide-deck.io https://www.googletagmanager.com https://www.google-analytics.com https://www.google.com https://www.googleadservices.com; font-src 'self'; connect-src 'self' https://cloudflareinsights.com https://us.i.posthog.com https://us-assets.i.posthog.com https://www.google-analytics.com https://*.google-analytics.com https://analytics.google.com https://www.googletagmanager.com https://stats.g.doubleclick.net https://www.google.com https://www.googleadservices.com https://googleads.g.doubleclick.net; object-src 'none'; base-uri 'self'; form-action 'self'; frame-src 'none'; media-src 'none'; manifest-src 'self'; worker-src 'self' blob:; frame-ancestors 'none'; report-uri /api/csp-report; report-to csp-endpoint
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Protected resource metadata

Retrieved No
Problem no_resource_metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://slide-deck.io/mcp Verified 200
http (plaintext) http://slide-deck.io/mcp HTTPS enforced 308 https://slide-deck.io/mcp
MCP tools · 3 exposed · ~392 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
generate_report ~180

Build a weekly status, project update, or quarterly report from a connected source. Native PowerPoint objects. Requires API key.

NameTypeReqDescription
csvstring–CSV text when source is csv: header row, first column = period/label, other columns numeric
kindstringyes–
pageIdstring––
projectIdstring––
projectKeystring––
repoFullNamestring––
sourcestringyesjira | github | notion | asana | linear | clickup | csv (pass the file contents in `csv`; spreadsheets: export as CSV)
spaceIdstring––
teamIdstring––
templateIdstring–Optional locked .pptx template id
titlestring–Deck title when source is csv

No output schema declared.

No examples provided.

list_connectors ~21

List live OAuth / file-import connectors this account can use.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

populate_template ~191

Fill a previously uploaded locked PowerPoint template from a connected source or a CSV / spreadsheet export. Masters stay. Charts stay charts. CSV fills are grounding-checked: every figure comes from the data.

NameTypeReqDescription
csvstring–CSV text when source is csv: header row, first column = period/label, other columns numeric
kindstringyes–
pageIdstring––
projectKeystring––
repoFullNamestring––
sourcestringyesjira | github | notion | asana | linear | clickup | csv (pass the file contents in `csv`; name charts csv_<column>; tokens like {{revenue_latest}}, {{revenue_change}}, {{label_1}}, {{revenue_1}})
templateIdstringyes–
titlestring–Report title when source is csv; fills {{title}}

No output schema declared.

No examples provided.

Install

How do I install the slide-deck.io MCP server?

slide-deck.io is a hosted endpoint at https://slide-deck.io/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 · slide-deck.io

# add to Claude Code
claude mcp add --transport http io-slide-deck-mcp 'https://slide-deck.io/mcp'
Common questions

What is the slide-deck.io MCP server?

slide-deck.io is an MCP server listed in the public MCP registry as io.slide-deck/mcp. Public remixable decks from a topic. Control.io product of Morton Technology Consulting, LLC. This page covers its hosted endpoint (https://slide-deck.io/mcp).

Is the slide-deck.io MCP server safe to use?

slide-deck.io scores 86 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 slide-deck.io MCP server expose?

slide-deck.io exposes 3 tools: generate_report, list_connectors, populate_template. Their descriptions and schemas cost roughly 392 tokens of context every time the server is loaded.

Does the slide-deck.io MCP server require authentication?

Yes. slide-deck.io asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the slide-deck.io MCP server still maintained?

slide-deck.io 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.