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.

Tellscreen

REMOTE · TELLSCREEN.COM

Turn screen recordings and video links into change lists with screenshots an AI can act on.

Available components

+3 this week 69 Trust /100

Last scanned (13 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

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 Security57
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 609 tokens (~152/item across 4 items; 4 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 Management37
  • Stability observed for 11 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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 (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 19 Nov 26 +1

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

  • 17 Nov 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.

  • 15 Nov 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.

  • 13 Nov 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.

  • 11 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 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 21 Nov 2026 · Probed https://tellscreen.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tellscreen.com CN=YE1,O=Let's Encrypt,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA384 6e2d1db4ab026a9dcf5d024c31546cd0b28
SANs: tellscreen.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tellscreen.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
tellscreen.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

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

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

Use when the user gives you a video FILE on their computer (a screen recording .mov/.mp4/.webm, a Loom or QuickTime download) that you cannot watch. This server cannot read local files, so this tool returns the exact one-line curl command that uploads the file and prints the change list as Markdown; run it with your shell tool. The result lists every change asked for, with the words said, where on screen, how to check it, a screenshot link of that moment, and the timed transcript.

NameTypeReqDescription
pathstringyesPath of the video file on the user's computer.

No output schema declared.

No examples provided.

convert_video_link ~210

Use when the user gives you a link to a video (a screen recording, product walkthrough, bug repro or design review: an .mp4/.mov/.webm URL, or a public Google Drive or Dropbox link) and you need to know what it shows or asks for, because you cannot watch video. Tellscreen transcribes it, looks at the screen at the moment each thing was said, and returns Markdown: a summary, every change asked for with the words said, where on screen, how to check it is done and a screenshot link of that moment, then the timed transcript. Waits up to 50 seconds; if it is still working you get a job id for get_change_list. Loom and YouTube pages cannot be fetched: ask the user for the downloaded file instead and use convert_local_video.

NameTypeReqDescription
titlestring–Optional title for the video.
urlstringyesDirect link to the video file, or a public Google Drive / Dropbox link.

No output schema declared.

No examples provided.

get_change_list ~108

Collect the result of record_screen or convert_video_link by job id. Waits up to 50 seconds; call it again while it says it is still working. Also accepts a tellscreen.com/v/ link to fetch the change list of an existing Tellscreen video.

NameTypeReqDescription
jobstring–The job id returned by record_screen or convert_video_link.
video_urlstring–Or: a tellscreen.com/v/… link (keep any ?agent= in it).

No output schema declared.

No examples provided.

record_screen ~88

Use when the user wants to show you something instead of typing it ("let me show you", "watch this", a bug they can reproduce, a design or product review). Returns a recording link for the user to open: they record their screen and talk through what should change, then press Stop. Then call get_change_list with the job id to receive the change list (it waits for them).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Tellscreen MCP server?

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

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

What is the Tellscreen MCP server?

Tellscreen is an MCP server listed in the public MCP registry as com.tellscreen/tellscreen. Turn screen recordings and video links into change lists with screenshots an AI can act on. This page covers its hosted endpoint (https://tellscreen.com/mcp).

Is the Tellscreen MCP server safe to use?

Tellscreen scores 69 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 Tellscreen MCP server expose?

Tellscreen exposes 4 tools: convert_video_link, convert_local_video, record_screen, get_change_list. Their descriptions and schemas cost roughly 538 tokens of context every time the server is loaded.

Does the Tellscreen MCP server require authentication?

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

Is the Tellscreen MCP server still maintained?

Tellscreen is still listed as active 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 Tellscreen MCP server?

VerifyMCP ran 12 checks on Tellscreen, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Tellscreen: Authorization. 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.