Skip to content
External endpointresponds

My TV Channel

Create and run 24/7 linear TV channels. Import videos by URL; we transcode, schedule and stream.

Endpoint URL
https://my-tv-channel.com/api/mytvchannel/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:05 AM UTC
Check
MCP initialize · 8s limit
Latency
522 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.my-tv-channel/my-tv-channel

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
my-tv-channel
Version
1.1.0
Capability keys
tools
Tool names
get_account_status, list_channels, get_channel, check_handle_available, create_channel, update_channel, archive_channel, import_video_from_url, import_youtube_video, list_assets, get_transcode_status, set_asset_weight, delete_asset, retry_transcode, regenerate_schedule, get_schedule, get_schedule_rules, validate_schedule_rules, set_schedule_rules
Instructions excerpt

Create and run 24/7 linear TV channels. Typical flow: get_account_status to learn the tier and quota, create_channel, import_video_from_url for each video (setting its weight as you go), poll get_transcode_status until meetsLaunchRequirements is true, then get_channel until scheduleStatus is 'active' and report {handle}.my-tv-channel.com to the owner. A channel needs 4+ ready videos and 15+ minutes before it can go live. If you change weights on an already-live channel, call regenerate_schedule or the change will not air.

Reported Aug 17, 2026, 05:05 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 320ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 946ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 545ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 522ms
Back to MCP directory