# Alto (remote · alto.video)

Send a finished video with one tracked link per recipient, and see who watched and how far.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `alto.video`: 32/100, [markdown](https://verifymcp.io/servers/video-alto-alto/alto.md), [page](https://verifymcp.io/servers/video-alto-alto/alto)
- remote · `alto.video`: 70/100 (this document), [markdown](https://verifymcp.io/servers/video-alto-alto/api-mcp.md), [page](https://verifymcp.io/servers/video-alto-alto/api-mcp)

## Channel facts

- Endpoint: `https://alto.video/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-10-07.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 874 tokens (~109/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Alto MCP server?

Alto is a hosted endpoint at https://alto.video/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.

### Claude

```bash
claude mcp add --transport http video-alto-alto 'https://alto.video/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "video-alto-alto": {
      "url": "https://alto.video/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "video-alto-alto": {
      "type": "http",
      "url": "https://alto.video/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.video-alto-alto]
url = "https://alto.video/api/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add video-alto-alto --url 'https://alto.video/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  video-alto-alto:
    url: "https://alto.video/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "video-alto-alto": {
      "Transport": "http",
      "Url": "https://alto.video/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add video-alto-alto -t streamable-http -u 'https://alto.video/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "video-alto-alto": {
      "type": "http",
      "url": "https://alto.video/api/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-10-07 (score 70, +1)

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

### 2026-10-04 (score 69, +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-10-02 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-01 (score 67)

First indexed and scored.

## MCP tools (8)

### `create_upload` (~117 tokens)

Start an upload

Start uploading a finished video (MP4, MOV or WebM) in parts. Returns an uploadId and one URL per part: PUT each part's exact bytes to its URL with the same Authorization header, keep the etag each PUT answers, then call complete_upload. Parts are partBytes long except the last.

Input parameters:

- `bytes` (integer, required): The file's size in bytes.
- `duration` (number): Length in seconds, if known.
- `type` (string, required): video/mp4, video/quicktime or video/webm.

### `complete_upload` (~179 tokens)

Finish an upload and send it

Join the parts of an upload started with create_upload, create the video, and make one tracked link per recipient. Returns the video, its share link and each recipient's link.

Input parameters:

- `description` (string)
- `duration` (number): Length in seconds. Needed unless Alto can measure the file.
- `parts` (array, required): Every part's { part, etag }, from the PUTs.
- `recipients` (array): Who to send it to: one tracked link each. Strings like "Dana Whitfield <dana@acme.example>", or objects { name, email, company, title, note }.
- `slug` (string): The readable part of the link, optional.
- `title` (string, required): What the prospect sees, e.g. "Fleet QA for Acme Logistics".
- `uploadId` (string, required)

### `upload_video` (~150 tokens)

Upload from a URL and send it

Upload a finished video that is already online (an https URL Alto can download, up to 2 GB), create it, and make one tracked link per recipient. For a file on your machine, use create_upload.

Input parameters:

- `description` (string)
- `duration` (number): Length in seconds. Needed unless Alto can measure the file.
- `recipients` (array): Who to send it to: one tracked link each. Strings like "Dana Whitfield <dana@acme.example>", or objects { name, email, company, title, note }.
- `slug` (string)
- `title` (string, required)
- `url` (string, required): An https URL of the video file.

### `create_link` (~130 tokens)

Make a recipient link

Make a tracked link to a video for one person, so every view is tied to them. Returns the link's URL to paste into an email.

Input parameters:

- `company` (string)
- `email` (string)
- `expiresInDays` (integer|null): Days until the link stops working; null never expires; left out uses the workspace default.
- `name` (string, required): Who it's for, e.g. "Dana Whitfield".
- `note` (string): A personal note shown on their demo page.
- `title` (string): Their job title.
- `videoId` (string, required)

### `get_moments` (~80 tokens)

How a video landed

Plays, how much people watched, how far each chapter reached and which one was rewatched, and where the most viewers left. Part of Pro's full API.

Input parameters:

- `since` (string): Only plays in this window: 90m, 24h, 7d, 2w.
- `videoId` (string, required)

### `list_viewers` (~48 tokens)

Who watched

Everyone who opened one of your links: recipients, people their links were forwarded to, and anonymous viewers, with how much they watched and whether they're watching now.

Input parameters:

- `filter` (string)

### `list_links` (~55 tokens)

Recipient links

Every recipient link, or one video's, with its status (watching, watched, opened, not opened, expired, disabled) and how much was watched.

Input parameters:

- `status` (string)
- `videoId` (string)

### `list_videos` (~27 tokens)

Your videos

Your library, newest first, with each video's id, title, share link and totals.

## Diagnostics

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

## Score history

- 2026-10-07: 70
- 2026-10-05: 69
- 2026-10-04: 69
- 2026-10-03: 68
- 2026-10-02: 68
- 2026-10-01: 67

## Common questions

### What is the Alto MCP server?

Alto is an MCP server listed in the public MCP registry as video.alto/alto. Send a finished video with one tracked link per recipient, and see who watched and how far. This page covers its hosted endpoint (https://alto.video/api/mcp).

### Is the Alto MCP server safe to use?

Alto scores 70 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 Alto MCP server expose?

Alto exposes 8 tools: create_upload, complete_upload, upload_video, create_link, get_moments, and 3 more. Their descriptions and schemas cost roughly 786 tokens of context every time the server is loaded.

### Does the Alto MCP server require authentication?

Yes. Alto 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 Alto MCP server still maintained?

Alto is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://alto.video/api/mcp
- Authorisation metadata: https://alto.video/.well-known/oauth-protected-resource/api/mcp
- Website: https://alto.video/docs/cli-and-mcp
- Changelog RSS feed: https://verifymcp.io/servers/video-alto-alto/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/video-alto-alto/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/video-alto-alto/api-mcp