Alto
REMOTE · ALTO.VIDEO · 2 COMPONENTS · SCANNED OCT 7
Send a finished video with one tracked link per recipient, and see who watched and how far.
Available components
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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 874 tokens (~109/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% 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 8 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · alto.video
claude mcp add --transport http video-alto-alto 'https://alto.video/api/mcp'
{
"mcpServers": {
"video-alto-alto": {
"url": "https://alto.video/api/mcp"
}
}
} {
"servers": {
"video-alto-alto": {
"type": "http",
"url": "https://alto.video/api/mcp"
}
}
} [mcp_servers.video-alto-alto] url = "https://alto.video/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"video-alto-alto": {
"type": "remote",
"url": "https://alto.video/api/mcp",
"enabled": true
}
}
} openclaw mcp add video-alto-alto --url 'https://alto.video/api/mcp' --transport streamable-http
mcp_servers:
video-alto-alto:
url: "https://alto.video/api/mcp" {
"McpServers": {
"video-alto-alto": {
"Transport": "http",
"Url": "https://alto.video/api/mcp"
}
}
} assistant mcp add video-alto-alto -t streamable-http -u 'https://alto.video/api/mcp'
{
"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.
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.
- 7 Oct 26 +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.
- 4 Oct 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.
- 2 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 1 Oct 26 67
First indexed and scored.
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 8 Oct 2026 · Probed https://alto.video/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=alto.video | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 2be104c894c8eb4e13ce98ed9ba56f2c |
| SANs: alto.video, *.alto.video | ||||||
| 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 alto.video. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| video. | present | 42529 | 8 | Verified |
| alto.video. | 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 |
WWW-Authenticate challenge Bearer realm="alto"
Bearer realm="alto"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://alto.video/api/mcp | Verified | 200 | |
| http (plaintext) | http://alto.video/api/mcp | Inconclusive | 405 |
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 →
complete_upload Finish an upload and send it ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| duration | number | – | Length in seconds. Needed unless Alto can measure the file. |
| parts | array | yes | 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 | yes | What the prospect sees, e.g. "Fleet QA for Acme Logistics". |
| uploadId | string | yes | – |
No output schema declared.
No examples provided.
create_link Make a recipient link ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| string | – | – | |
| expiresInDays | integer|null | – | Days until the link stops working; null never expires; left out uses the workspace default. |
| name | string | yes | 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 | yes | – |
No output schema declared.
No examples provided.
create_upload Start an upload ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | The file's size in bytes. |
| duration | number | – | Length in seconds, if known. |
| type | string | yes | video/mp4, video/quicktime or video/webm. |
No output schema declared.
No examples provided.
get_moments How a video landed ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | Only plays in this window: 90m, 24h, 7d, 2w. |
| videoId | string | yes | – |
No output schema declared.
No examples provided.
list_links Recipient links ~55
Every recipient link, or one video's, with its status (watching, watched, opened, not opened, expired, disabled) and how much was watched.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
| videoId | string | – | – |
No output schema declared.
No examples provided.
list_videos Your videos ~27
Your library, newest first, with each video's id, title, share link and totals.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_viewers Who watched ~48
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | – |
No output schema declared.
No examples provided.
upload_video Upload from a URL and send it ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| url | string | yes | An https URL of the video file. |
No output schema declared.
No examples provided.
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.