# Tellscreen (remote · tellscreen.com)

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

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `tellscreen.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-tellscreen-tellscreen/tellscreen.md), [page](https://verifymcp.io/servers/com-tellscreen-tellscreen/tellscreen)

## Channel facts

- Endpoint: `https://tellscreen.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-tellscreen-tellscreen 'https://tellscreen.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-tellscreen-tellscreen": {
      "url": "https://tellscreen.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-tellscreen-tellscreen": {
      "type": "http",
      "url": "https://tellscreen.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-tellscreen-tellscreen]
url = "https://tellscreen.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-tellscreen-tellscreen": {
      "type": "remote",
      "url": "https://tellscreen.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-tellscreen-tellscreen --url 'https://tellscreen.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-tellscreen-tellscreen:
    url: "https://tellscreen.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-tellscreen-tellscreen": {
      "Transport": "http",
      "Url": "https://tellscreen.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-tellscreen-tellscreen -t streamable-http -u 'https://tellscreen.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-tellscreen-tellscreen": {
      "type": "http",
      "url": "https://tellscreen.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 69, +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.

### 2026-11-17 (score 68, +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.

### 2026-11-15 (score 67, +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.

### 2026-11-13 (score 66, +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.

### 2026-11-11 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 64)

First indexed and scored.

## MCP tools (4)

### `convert_video_link` (~210 tokens)

Turn a video link into a change list

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.

Input parameters:

- `title` (string): Optional title for the video.
- `url` (string, required): Direct link to the video file, or a public Google Drive / Dropbox link.

### `convert_local_video` (~132 tokens)

Turn a video file on this computer into a change list

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.

Input parameters:

- `path` (string, required): Path of the video file on the user's computer.

### `record_screen` (~88 tokens)

Ask the user to show you on screen

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).

### `get_change_list` (~108 tokens)

Collect a change list

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.

Input parameters:

- `job` (string): The job id returned by record_screen or convert_video_link.
- `video_url` (string): Or: a tellscreen.com/v/… link (keep any ?agent= in it).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-tellscreen-tellscreen/tellscreen#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 68
- 2026-11-17: 68
- 2026-11-16: 67
- 2026-11-15: 67
- 2026-11-14: 66
- 2026-11-13: 66
- 2026-11-12: 65
- 2026-11-11: 65
- 2026-11-10: 64

## 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.

## Links

- Remote endpoint: https://tellscreen.com/mcp
- Website: https://tellscreen.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-tellscreen-tellscreen/tellscreen.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-tellscreen-tellscreen/tellscreen/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-tellscreen-tellscreen/tellscreen.json
- HTML version of this page: https://verifymcp.io/servers/com-tellscreen-tellscreen/tellscreen
