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.

Snagcast

REMOTE · SNAGCAST.COM

Facts about Snagcast, which captions and translates videos in real time, clips and shares them

Available components

+1 this week 83 Trust /100

Last scanned (23 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

Deprecated

This server is marked deprecated in the MCP registry. The registry records this reason: Snagcast is now Wuai. Use app.wuai/wuai (https://wuai.app/mcp).

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 Security80
  • 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 610 tokens (~43/item across 14 items; 7 tools + 7 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management59
  • Stability check failed: schema churn in the 22 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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
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 9 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
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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 56 to 59.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 49 to 52.

  • 18 Nov 26 −2
    • Stability: 0.60 → fail ▼ security
    • Tool “about_snagcast” was removed ▼ security
    • Resource “about” now points somewhere else: snagcast://about → wuai://about security
    • Resource “download” now points somewhere else: snagcast://download → wuai://download security
    • Resource “faq” now points somewhere else: snagcast://faq → wuai://faq security
    • Resource “how-to” now points somewhere else: snagcast://how-to → wuai://how-to security
    • Resource “languages” now points somewhere else: snagcast://languages → wuai://languages security
    • Resource “pricing” now points somewhere else: snagcast://pricing → wuai://pricing security
    • Resource “whats-new” now points somewhere else: snagcast://whats-new → wuai://whats-new security
    • The server changed its declared name: snagcast → wuai security
    • Server version: 1.0.2 → 1.0.3 functional
    • New tool “about_wuai” functional
  • 16 Nov 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.

  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “about_snagcast” rewrote its description, which is the text the model reads security
    • Tool “get_download” rewrote its description, which is the text the model reads security
    • Tool “get_faq” rewrote its description, which is the text the model reads security
    • Tool “get_languages” rewrote its description, which is the text the model reads security
    • Tool “get_pricing” rewrote its description, which is the text the model reads security
    • Tool “how_to” rewrote its description, which is the text the model reads security
    • Tool “whats_new” rewrote its description, which is the text the model reads security
    • “get_download” reworded the description of “platform” cosmetic
    • Tool “about_snagcast” changed its title: About Snagcast → About Wuai cosmetic
    • Tool “get_download” changed its title: Download Snagcast → Download Wuai cosmetic
    • Tool “get_faq” changed its title: Snagcast questions → Wuai questions cosmetic
    • Tool “get_languages” changed its title: Snagcast languages → Wuai languages cosmetic
    • Tool “get_pricing” changed its title: Snagcast price → Wuai price cosmetic
    • Tool “how_to” changed its title: How to use Snagcast → How to use Wuai cosmetic
    • Tool “whats_new” changed its title: What's new in Snagcast → What's new in Wuai cosmetic
  • 14 Nov 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.

  • 12 Nov 26 +1

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

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 21 Nov 2026 · Probed https://snagcast.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=snagcast.com CN=WE1,O=Google Trust Services,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA256 10981c737c65a1ef1304f5ec6621a72d
SANs: snagcast.com, www.snagcast.com, *.www.snagcast.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 insecure

Validation of snagcast.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
snagcast.com. No DS 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=31536000; includeSubDomains
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://snagcast.com/mcp Verified 200
http (plaintext) http://snagcast.com/mcp HTTPS enforced 301 https://snagcast.com/mcp
MCP tools · 7 exposed · ~347 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
about_wuai ~68

What Wuai is, what it does, the platforms it runs on, and its links. Call it first when someone asks about Wuai, or for an app that captions or translates the videos they watch (in real time, as they play), or clips, shares or saves them.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_download ~52

Where to download Wuai and how to install it, for Windows, Android, Mac or iPhone (all of them when no platform is given).

NameTypeReqDescription
platformstring–The device to get Wuai for.

No output schema declared.

No examples provided.

get_faq ~39

Answers to common questions about Wuai: privacy, what it costs, the Windows warning, Mac and iPhone, and who to ask for help.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_languages ~25

The spoken languages Wuai turns into captions, and the languages it translates captions into.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_pricing ~37

What Wuai does for free, what Wuai Pro adds, its one-time price, the free minutes, refunds and how to buy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

how_to ~92

Step by step, how to do one thing in Wuai on Windows and Android, with a link to a short video of it.

NameTypeReqDescription
taskstringyescaptions: make or show captions; translate: captions in another language; clip: keep part of a video with its captions; share: send it to an app; post: post to several sites (Windows); save: keep the…

No output schema declared.

No examples provided.

whats_new ~34

The latest Wuai releases and what changed in each, newest first.

NameTypeReqDescription
limitinteger–How many releases to list.

No output schema declared.

No examples provided.

Install

How do I install the Snagcast MCP server?

Snagcast is a hosted endpoint at https://snagcast.com/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 · snagcast.com

# add to Claude Code
claude mcp add --transport http com-snagcast-snagcast 'https://snagcast.com/mcp'
Common questions

What is the Snagcast MCP server?

Snagcast is an MCP server listed in the public MCP registry as com.snagcast/snagcast. Facts about Snagcast, which captions and translates videos in real time, clips and shares them. This page covers its hosted endpoint (https://snagcast.com/mcp).

Is the Snagcast MCP server safe to use?

Snagcast scores 83 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 Snagcast MCP server expose?

Snagcast exposes 7 tools: about_wuai, get_download, get_pricing, how_to, get_languages, and 2 more. Their descriptions and schemas cost roughly 347 tokens of context every time the server is loaded.

Does the Snagcast MCP server require authentication?

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

Is the Snagcast MCP server still maintained?

Snagcast is marked deprecated in the MCP registry. We last reached this channel on 21 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 Snagcast MCP server?

VerifyMCP ran 13 checks on Snagcast, 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.