Vídeos temporales MCP server

Which servers in the official MCP registry are Vídeos temporales's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to Vídeos temporales

Whose server it is

Registry namenet.videostemporales/video-temporary-hostingverified in the MCP registry

The registry name sits under videostemporales.net. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20

Stateanswerschecked 2026-10-20
Tools2
Server calls itselfvideostemporales
Server version1.0.0
Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 531 ms.

Measured dailydaily checks: 1, the first on 2026-10-20

Answeredmeasuring1 of the 7 daily checks it takes to print a share
Median first answer524 ms
Space in an agent's context≈ 396 tokensthe definitions of all its tools (2), which an agent carries on every turn
Tool definitionsA · 92 of 100

Parameters without a description: in 1 of 2

Worth a look

Tools that change data, on a server that answers without a sign-in: upload_temporary_video

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-20

get_upload_limits
Returns the current size, quota, file-type and expiration limits for this VideosTemporales agent integration.
upload_temporary_video
Uploads a user-provided video to VideosTemporales and returns a temporary human viewing page. Always give the returned share_url to the user exactly; never construct or expose a direct media URL.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "video-temporary-hosting": {
      "type": "http",
      "url": "https://mcp.videostemporales.net/"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.