Create and run 24/7 linear TV channels — the kind that just play, with no menu to browse. Import videos by URL, shape the rotation with per-video weights, and the service transcodes and schedules them into a continuous broadcast at `{handle}.my-tv-channel.com`, watchable on the web and in the iOS, tvOS, macOS, Android, Fire TV and Roku apps. **What your agent can do** - Create a channel and check the handle is free - Import videos from any direct media URL, or from YouTube videos the owner proves they own - Set how often each video plays (weight 0–10) and regenerate the schedule to apply it - Read the EPG, and on Pro tiers set fixed slots and dayparts ("cartoons 6–9am weekdays, news at 6pm") - Poll transcode progress and see exactly what a channel still needs before it goes live A channel goes live automatically once it has 4 ready videos and 15 minutes of content. **Note:** you cannot upload local files over MCP — tool arguments are JSON, so there is no multipart channel. Use `import_video_from_url` with a public URL; local files go through the apps. Requires a My TV Channel API key (any subscription tier). Create one at https://my-tv-channel.com/agent-keys/

MCP readiness

B · 83/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 87.7/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (590 ms).
Protocol revision	6/10	Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	22/22 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 19 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (590 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 60% of peers; This listing 83 · peer median 81
Latency: Faster than 34% of peers; This listing 467 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
Protocol revision −4 — Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

agenstry since 2026-10-22 ↗

How to connect

MCP endpoint (streamable-http)

https://my-tv-channel.com/mcp

JSON-RPC initialize probe

curl -X POST https://my-tv-channel.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://my-tv-channel.com

Listed at (agenstry)

https://agenstry.com/mcp/my-tv-channel/my-tv-channel