Skip to content

broadcast MCP server

global.rootz.dtv/broadcastdtv.rootz.globalstreamable-httpv0.1.0Scanned

Which TV transmitters actually reach an address, terrain-graded, and what is on now.

9 tools: 8 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 8 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the broadcast MCP server can do

The broadcast MCP server is published by dtv.rootz.global, a domain the MCP Registry verified. It has 9 tools. It can create or change data (8 tools: media_whats_on, media_receivable, media_still_true, media_closed and 4 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 8Claude Code: ask
  • media_closedChannels that have shut down, with the date they closed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Channels that have shut down, with the date they closed. Useful for checking whether a channel a model remembers still exists.
  • media_freshnessHow current this dataset is: when each source last ran, how many assertions are live versus expired, and the gaps we know we have.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    How current this dataset is: when each source last ran, how many assertions are live versus expired, and the gaps we know we have.
  • media_receivableWhich television transmitters reach a specific latitude and longitude, graded by real terrain between the tower and that point.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Which television transmitters reach a specific latitude and longitude, graded by real terrain between the tower and that point. Answers "what can I actually watch from here", which listings services cannot.
  • media_sourcesWhere the data comes from, each with its licence and whether it may be redistributed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Where the data comes from, each with its licence and whether it may be redistributed.
  • media_station_readinessWhether a US television station website can be read by an AI assistant: which AI crawlers it blocks by name in robots.txt, whether it publishes llms.txt or /.well-known/ai, and whe…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Whether a US television station website can be read by an AI assistant: which AI crawlers it blocks by name in robots.txt, whether it publishes llms.txt or /.well-known/ai, and whether it has structured data. Pass a callsign for one station, or nothing for the industry-wide summary broken down by owner group.
  • media_still_trueIs a remembered claim about a programme still current?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Is a remembered claim about a programme still current? Returns when it was observed, whether it has expired, and what replaced it. This is the question a model cannot answer about its own training data.
  • media_verifyVerify a signed record from this service.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify a signed record from this service. Pass an airing_id, or pass back a record you cached earlier with its signature and we will confirm it is byte-identical to what we signed. The public key and exact canonicalisation are at /.well-known/dtv-intel-signing.json so you can also verify offline without calling us.
  • media_whats_onWhat is airing right now, or at a given time.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    What is airing right now, or at a given time. Returns programmes with descriptions and, for each, when the claim was observed and when it expires. Accepts free text.
Only reads 1Show 1 read-only tool
  • media_outletsSearch stations, networks and streaming channels by name, callsign, network or owner.No findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.
    Description, as the server wrote it
    Search stations, networks and streaming channels by name, callsign, network or owner. Returns licence status, transmitter power and antenna height where filed.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://dtv.rootz.global/mcp: tools/list returned 9 tools to an anonymous client, including media_whats_on (write), media_receivable (write), media_still_true (write), media_closed (write), media_verify (write) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http broadcast https://dtv.rootz.global/mcp
claude mcp add --transport http broadcast https://dtv.rootz.global/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__broadcast__media_outlets"
    ],
    "ask": [
      "mcp__broadcast__media_whats_on",
      "mcp__broadcast__media_receivable",
      "mcp__broadcast__media_still_true",
      "mcp__broadcast__media_closed",
      "mcp__broadcast__media_verify",
      "mcp__broadcast__media_station_readiness",
      "mcp__broadcast__media_freshness",
      "mcp__broadcast__media_sources"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as broadcast. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/global.rootz.dtv/broadcast/verify?hash=99e23a514491757a70ec68f3db0e38feb6b59efc0f355bd08c0dc8b93898b9b2" | jq -e '.changed == false'

Pinned hash 99e23a514491, from Nov 17, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/global.rootz.dtv/broadcast/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for global.rootz.dtv/broadcast
[![Anlyon Radar](https://radar.anlyon.com/badge/global.rootz.dtv/broadcast.svg)](https://radar.anlyon.com/servers/global.rootz.dtv/broadcast)

Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.

broadcast MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the broadcast MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the broadcast MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the broadcast MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the broadcast MCP server have?

9 tools: 8 write, 1 read. media_whats_on, media_receivable, media_still_true, media_closed, media_verify, media_station_readiness, media_freshness, media_sources and 1 more.

Does the broadcast MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the broadcast MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the broadcast MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.