Is the Rootz Dtv Broadcast MCP server down?

mcp-registry/global.rootz.dtv/broadcast · v0.1.0

As of 2026-10-21 09:49 UTC, the Rootz Dtv Broadcast MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 8 minutes.

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

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

{
  "mcpServers": {
    "rootz-dtv-broadcast-mcp-server": {
      "type": "http",
      "url": "https://dtv.rootz.global/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (68/100)

What to fix (4)

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 9 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fglobal.rootz.dtv%2Fbroadcast/fixes

{
  "name": "media_closed",
  "description": "Channels that have shut down, with the date they closed. Useful for checking whether a channel a model remembers still exists.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "number"
      },
      "query": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}

{
  "name": "media_station_readiness",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "A callsign such as WNYT, or free text. Omit for the summary."
      },
      "callsign": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/global.rootz.dtv/broadcast"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/global.rootz.dtv/broadcast"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~1,165 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.92% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• media_verify ~217 tokens
• media_receivable ~204 tokens
• media_station_readiness ~150 tokens
• media_whats_on ~147 tokens
• media_outlets ~132 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fglobal.rootz.dtv%2Fbroadcast.svg)](https://glimind.com/server/mcp-registry%2Fglobal.rootz.dtv%2Fbroadcast?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fglobal.rootz.dtv%2Fbroadcast?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fglobal.rootz.dtv%2Fbroadcast.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fglobal.rootz.dtv%2Fbroadcast.svg
   :target: https://glimind.com/server/mcp-registry%2Fglobal.rootz.dtv%2Fbroadcast?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3484b11cae7e1bc2…, first seen 2026-10-17, included at leaf 12119 of 38,850. Version history · verify what your client received.

Tools (9)

• media_closed
• media_freshness
• media_outlets
• media_receivable
• media_sources
• media_station_readiness
• media_still_true
• media_verify
• media_whats_on

Compare: most reliable media servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Rootz Dtv Broadcast MCP server down right now?

As of 2026-10-21 09:49 UTC, the Rootz Dtv Broadcast MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Rootz Dtv Broadcast MCP server provide?

Rootz Dtv Broadcast MCP server advertises 9 tools, including media_closed, media_freshness, media_outlets, media_receivable, media_sources.

How do I install Rootz Dtv Broadcast MCP server?

Point your MCP client at this streamable-http endpoint: https://dtv.rootz.global/mcp

Is the Rootz Dtv Broadcast MCP server safe to connect to an AI agent?

Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Rootz Dtv Broadcast MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.