# My TV Channel (remote · my-tv-channel.com)

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

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `my-tv-channel.com`: 60/100 (this document), [markdown](https://verifymcp.io/servers/com-my-tv-channel-my-tv-channel/api-mytvchannel-mcp.md), [page](https://verifymcp.io/servers/com-my-tv-channel-my-tv-channel/api-mytvchannel-mcp)

## Channel facts

- Endpoint: `https://my-tv-channel.com/api/mytvchannel/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-08-03.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (archive_channel).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2572 tokens (~135/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-my-tv-channel-my-tv-channel https://my-tv-channel.com/api/mytvchannel/mcp
```

### Codex

```toml
[mcp_servers.com-my-tv-channel-my-tv-channel]
url = "https://my-tv-channel.com/api/mytvchannel/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-my-tv-channel-my-tv-channel": {
      "type": "remote",
      "url": "https://my-tv-channel.com/api/mytvchannel/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-my-tv-channel-my-tv-channel --url https://my-tv-channel.com/api/mytvchannel/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-my-tv-channel-my-tv-channel:
    url: "https://my-tv-channel.com/api/mytvchannel/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-my-tv-channel-my-tv-channel": {
      "type": "http",
      "url": "https://my-tv-channel.com/api/mytvchannel/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-08-02 (score 60, +10)

- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Stability: unverified → 0.03

### 2026-08-01 (score 50)

First indexed and scored.

## MCP tools (19)

### `get_account_status` (~79 tokens)

Start here. Returns who the account is, its subscription tier and limits, how much weekly upload/stream quota is used and remaining, and every channel the owner has with its ready-asset count and what it still needs to go live (launchGaps). Call this before creating anything so you know the real limits for THIS account rather than assuming.

### `list_channels` (~16 tokens)

List the channels owned by this account.

### `get_channel` (~57 tokens)

Get one channel by id. Includes scheduleStatus (inactive | pending | active | error) — poll this to confirm a channel has gone live — plus watchUrl, launchedAt and isArchived.

Input parameters:

- `channel_id` (integer, required): Channel id

### `check_handle_available` (~74 tokens)

Check whether a channel handle is free before trying to create it. The handle becomes the subdomain: {handle}.my-tv-channel.com. 3-63 chars, lowercase a-z, 0-9 and hyphens.

Input parameters:

- `handle` (string, required): Desired handle, e.g. "retro-arcade"

### `create_channel` (~217 tokens)

Create a 24/7 linear TV channel. It will NOT be live yet — a channel goes live automatically once it has at least 4 ready assets AND at least 15 minutes of total content. is_public lists it in Discover and is available on every subscription tier, including Starter.

Input parameters:

- `category` (string)
- `channel_type` (string, required): Use "thematic" unless the channel is tied to a place
- `description` (string)
- `handle` (string, required): 3-63 chars, lowercase a-z 0-9 and hyphens. Becomes {handle}.my-tv-channel.com
- `is_public` (boolean): List in Discover. Available on all tiers.
- `location` (object): Required only when channel_type is "location"
- `name` (string, required): Display name
- `orientation` (string): vertical = 9:16
- `primary_language` (string): ISO 639-1, e.g. "en", "fr"
- `tags` (array)

### `update_channel` (~221 tokens)

Update an existing channel: name, description, visibility, category, language, age rating, or the community chat link. Only send the fields you are changing.

Input parameters:

- `age_classification` (string)
- `allow_offline_download` (boolean)
- `category` (string)
- `channel_id` (integer, required)
- `chat_channel_id` (string): Discord channel id within that server
- `chat_platform` (string): Community chat platform shown as an overlay on the player. Discord is the fully supported one; the others are accepted but only Discord has a working embed today.
- `chat_server_id` (string): Discord server (guild) id — the owner must supply this; you cannot discover it
- `description` (string)
- `is_public` (boolean): List in Discover. Allowed on every tier.
- `keywords` (string): Multilingual search keywords
- `name` (string)
- `primary_language` (string): ISO 639-1, e.g. "en"
- `show_schedule` (boolean)

### `archive_channel` (~87 tokens)

Take a channel off the air and out of every listing. This ARCHIVES rather than destroys: the handle stays reserved and assets and schedule history are retained, so it can be restored. Refuses with 409 while transcodes are still running. Idempotent. This is the reversible way to take a channel down; delete_asset removes individual videos instead.

Input parameters:

- `channel_id` (integer, required)

### `import_video_from_url` (~244 tokens)

Add a video to a channel from a direct media URL. THIS IS THE MAIN WAY TO ADD CONTENT over MCP — you cannot upload local file bytes through this interface, so if the owner has local files, ask them to host them somewhere reachable or upload via the app. The URL must be a direct, public, unauthenticated link to mp4/mov/m4v/mpeg/mpg/avi, or a FINITE .m3u8 (VOD, not a live stream) — not a web page, not behind a login, not a YouTube/Vimeo watch page. The server downloads it. Returns immediately; the asset then goes downloading -> pending -> transcoding -> ready. Duration counts against the weekly upload quota. Re-submitting the same URL to the same channel returns the original asset instead of importing twice.

Input parameters:

- `channel_id` (integer, required)
- `tags` (array)
- `title` (string)
- `url` (string, required): Direct, public media URL
- `weight` (integer): How often it plays, 0-10 (default 5). Set it here rather than after — see set_asset_weight.

### `import_youtube_video` (~244 tokens)

Import a YouTube video that the OWNER UPLOADED THEMSELVES. This will not work for anyone else's video, by design — a channel built from other people's videos is a copyright problem for the owner.

Ownership is proved by a tag only the uploader can add:
  1\. The owner's tag looks like 'MyTVChannelApp#<device-id>'. When the import fails for a missing tag, the 403 error message contains that account's exact tag string.
  2\. They paste that exact string into the video's description or tags on YouTube.
  3\. Retry the import.

You cannot do step 2 for them and you cannot bypass it. Public finished videos only: no live streams, no private or age-restricted videos, no playlists or channel URLs. Capped at 10 per day. Counts against the same weekly upload quota as everything else.

Input parameters:

- `channel_id` (integer, required)
- `tags` (array)
- `title` (string): Overrides the YouTube title
- `url` (string, required): A single-video YouTube URL (watch, shorts or youtu.be)
- `weight` (integer)

### `list_assets` (~23 tokens)

List the videos on a channel.

Input parameters:

- `channel_id` (integer, required)

### `get_transcode_status` (~102 tokens)

Poll transcode progress. Give either channel_id (all its videos) or asset_id (one). Each asset reports uploadStatus (downloading -> pending -> transcoding -> ready) and the summary tells you when meetsLaunchRequirements becomes true: 4+ ready assets AND 900+ seconds. Poll every 30-60s; transcoding takes roughly real-time/4.

Input parameters:

- `asset_id` (integer)
- `channel_id` (integer)

### `set_asset_weight` (~184 tokens)

Change how often a video plays (weight 0-10, default 5; 0 removes it from rotation entirely), and optionally its title or tags. IMPORTANT ORDERING: weights only affect what actually airs when the schedule is (re)generated. A channel builds its schedule the instant it crosses the launch threshold, so weights set AFTER that are stored but do not air. Either set the weight when you import each video, or call regenerate_schedule afterwards. Weights are relative: identical weights across every video produce a uniform rotation, and the spread between them is what shapes airtime.

Input parameters:

- `asset_id` (integer, required)
- `tags` (array): Tag videos seqXX01, seqXX02 … (XX = any two letters) to force them to play in order as a mini-series.
- `title` (string)
- `weight` (integer)

### `delete_asset` (~71 tokens)

Remove a video from a channel. Soft delete — it stops being scheduled immediately and the schedule regenerates automatically. Idempotent. The asset is retained and stops being scheduled; it is not erased. Affects one video — archive_channel takes a whole channel off the air.

Input parameters:

- `asset_id` (integer, required)

### `retry_transcode` (~36 tokens)

Re-queue a video whose transcode failed. Only works on assets in a failed state.

Input parameters:

- `asset_id` (integer, required)

### `regenerate_schedule` (~90 tokens)

Rebuild the channel's schedule now using the current weights. Call this after changing weights on a channel that is ALREADY live, otherwise the change will not air until the hourly cron. Throttled to one call per channel per 5 minutes; exceeding that returns 429 with a Retry-After header giving the seconds remaining. Requires the channel to meet launch requirements.

Input parameters:

- `channel_id` (integer, required)

### `get_schedule` (~52 tokens)

Read the channel's EPG — what is playing and what is coming up. Note this one returns a plain array of entries (unlike other tools, which return an object).

Input parameters:

- `channel_id` (integer, required)

### `get_schedule_rules` (~40 tokens)

Read the channel's declarative schedule rules (fixed time slots and dayparts), plus its scheduling mode and timezone.

Input parameters:

- `channel_id` (integer, required)

### `validate_schedule_rules` (~172 tokens)

DRY-RUN a ruleset. Saves nothing. Returns {valid, errors, warnings, preview} where preview is a simulated 24h grid of what would actually air. Intended as the dry run for set_schedule_rules: rules are wall-clock, slots start on-or-after their time, and dayparts reweight the random fill, so the airing result is hard to predict from the rules alone. Unlike set_schedule_rules this is not tier-gated and works on any tier. Same payload as set_schedule_rules.

Input parameters:

- `channel_id` (integer, required)
- `hours` (integer): How many hours to simulate (default 24, max 168)
- `rules` (array, required): Same shape as set_schedule_rules
- `timezone` (string): IANA name, e.g. "Europe/Paris"

### `set_schedule_rules` (~444 tokens)

Give the channel a durable schedule: fixed slots ("news at 18:00") and dayparts ("no kids content after 22:00"). The scheduler re-honours these on EVERY rebuild, so you set them once instead of babysitting the grid. **Pro tier or higher.**

This REPLACES the entire ruleset — send every rule you want, not just new ones. Sending an empty array removes all rules and returns the channel to plain weighted-random. Validate first with validate_schedule_rules.

Rule shapes:
  time_slot      {rule_type:'time_slot', start_time:'18:00', end_time?:'21:00',
                  days_mask:127, selector_type:'asset'|'tag'|'playlist',
                  selector_value:<id|tag|[ids]>, priority?:0}
  daypart_weight {rule_type:'daypart_weight', start_time:'22:00', end_time:'06:00',
                  days_mask:127, selector_type:'asset'|'tag', selector_value:...,
                  weight_multiplier:0-10}

days_mask is a bitmask: bit0=Mon … bit6=Sun. 127=daily, 31=Mon-Fri, 96=weekend.
end_time on a time_slot makes it a BLOCK that keeps drawing from the selector until that time — that is how you get 'cartoons 06:00-09:00' rather than one cartoon.
selector_type 'playlist' with an array of asset ids plays them IN ORDER.
weight_multiplier 0 removes matching assets from that window entirely.

Set `timezone` (IANA) or the times mean UTC, which is almost never what the owner meant. Slots start ON-OR-AFTER their time: the programme running into a slot is never cut short, so an 18:00 slot may begin at 18:02. That is intended.

Input parameters:

- `channel_id` (integer, required)
- `rules` (array, required): The COMPLETE ruleset. Empty array clears all rules.
- `timezone` (string): IANA name, e.g. "Europe/Paris". Strongly recommended.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-my-tv-channel-my-tv-channel/api-mytvchannel-mcp#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 60
- 2026-08-01: 50

## Links

- Remote endpoint: https://my-tv-channel.com/api/mytvchannel/mcp
- Authorisation metadata: https://my-tv-channel.com/.well-known/oauth-protected-resource/api/mytvchannel/mcp
- Website: https://my-tv-channel.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-my-tv-channel-my-tv-channel/api-mytvchannel-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-my-tv-channel-my-tv-channel/api-mytvchannel-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-my-tv-channel-my-tv-channel/api-mytvchannel-mcp