Remote MCP · Endpoint

Nova Cast MCP server

No. Nova Cast answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://nova.ardabot.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.r4v3n-art/nova-cast
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
93 ms
Tools exposed
28 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Give your AI agent the power to cast to your home TV and control an interactive canvas. By ArdaBot.
Listing
From the official MCP registry (active).
Recent checks of Nova Cast
CheckedResultHandshake
1 hour agoHandshake completed93 ms
2 days agoHandshake completed75 ms
4 days agoHandshake completed58 ms
6 days agoHandshake completed60 ms
8 days agoHandshake completed57 ms
10 days agoHandshake completed57 ms
12 days agoHandshake completed171 ms
14 days agoHandshake completed61 ms
15 days agoHandshake completed61 ms
16 days agoHandshake completed59 ms
17 days agoHandshake completed77 ms
20 days agoHandshake completed63 ms
22 days agoHandshake completed79 ms
23 days agoHandshake completed76 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Nova Cast and makes no claim about it beyond what these checks measured.