_ registry / mcp streamable-http · checked 2h ago

alto

https://alto.video

Registry code: 9889af6831256a04

api record

Alto hosts finished demo videos and sends one tracked link per recipient. To upload: call create_upload with the file's size and type, PUT each part to the URLs it returns with the same Authorization header, then call complete_upload with a title and the recipients. For a file already online, upload_video takes its https URL. create_link makes another recipient link; get_moments and list_viewers say how it landed.

endpoint
https://alto.video/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is alto live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is alto free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does alto have?
8 tools: list_videos, list_viewers, list_links, get_moments, create_upload, complete_upload, upload_video, create_link.
Is alto safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.9%

90 days 99.3%· all time 99.3%

latency
709ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 281 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
productivity & business crm & sales
used for
  • upload a demo video
  • create a tracked video link per recipient
  • see who watched a video and how much
takes → gives
video, text → data
tools
4 reads4 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
8 auth-required 8 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_videos reads auth-required 5h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_viewers reads auth-required 5h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "filter": {
      "enum": [
        "watching",
        "engaged",
        "dropped"
      ],
      "type": "string"
    }
  }
}
    arguments 13 lines
  • list_links reads auth-required 5h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "status": {
      "type": "string"
    },
    "videoId": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • get_moments reads auth-required 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "videoId"
  ],
  "properties": {
    "since": {
      "type": "string",
      "description": "Only plays in this window: 90m, 24h, 7d, 2w."
    },
    "videoId": {
      "type": "string"
    }
  }
}
    arguments 15 lines
  • create_upload changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "bytes",
    "type"
  ],
  "properties": {
    "type": {
      "type": "string",
      "description": "video/mp4, video/quicktime or video/webm."
    },
    "bytes": {
      "type": "integer",
      "description": "The file's size in bytes."
    },
    "duration": {
      "type": "number",
      "description": "Length in seconds, if known."
    }
  }
}
    arguments 21 lines
  • complete_upload changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "uploadId",
    "parts",
    "title"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The readable part of the link, optional."
    },
    "parts": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "etag": {
            "type": "string"
          },
          "part": {
            "type": "integer"
          }
        }
      },
      "description": "Every part's { part, etag }, from the PUTs."
    },
    "title": {
      "type": "string",
      "description": "What the prospect sees, e.g. \"Fleet QA for Pruitt Logistics\"."
    },
    "duration": {
      "type": "number",
      "description": "Length in seconds. Needed unless Alto can measure the file."
    },
    "uploadId": {
      "type": "string"
    },
    "recipients": {
      "type": "array",
      "items": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "object",
            "properties": {
              "name": {
                "type": "string"
              },
              "note": {
                "type": "string"
              },
              "email": {
                "type": "string"
              },
              "title": {
                "type": "string"
              },
              "company": {
                "type": "string"
              }
            }
          }
        ]
      },
      "description": "Who to send it to: one tracked link each. Strings like \"Michelle Barba <[email protected]>\", or objects { name, email, company, title, note }."
    },
    "description": {
      "type": "string"
    }
  }
}
    arguments 74 lines
  • upload_video changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url",
    "title"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "An https URL of the video file."
    },
    "slug": {
      "type": "string"
    },
    "title": {
      "type": "string"
    },
    "duration": {
      "type": "number",
      "description": "Length in seconds. Needed unless Alto can measure the file."
    },
    "recipients": {
      "type": "array",
      "items": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "object",
            "properties": {
              "name": {
                "type": "string"
              },
              "note": {
                "type": "string"
              },
              "email": {
                "type": "string"
              },
              "title": {
                "type": "string"
              },
              "company": {
                "type": "string"
              }
            }
          }
        ]
      },
      "description": "Who to send it to: one tracked link each. Strings like \"Michelle Barba <[email protected]>\", or objects { name, email, company, title, note }."
    },
    "description": {
      "type": "string"
    }
  }
}
    arguments 57 lines
  • create_link changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "videoId",
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Who it's for, e.g. \"Michelle Barba\"."
    },
    "note": {
      "type": "string",
      "description": "A personal note shown on their demo page."
    },
    "email": {
      "type": "string"
    },
    "title": {
      "type": "string",
      "description": "Their job title."
    },
    "company": {
      "type": "string"
    },
    "videoId": {
      "type": "string"
    },
    "expiresInDays": {
      "type": [
        "integer",
        "null"
      ],
      "description": "Days until the link stops working; null never expires; left out uses the workspace default."
    }
  }
}
    arguments 37 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9889af6831256a04.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9889af6831256a04/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9889af6831256a04/badge.svg)](https://brick.blue/agent/9889af6831256a04?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.