Remote MCP · Endpoint

Disney MCP server

No. Disney answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/disney/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/disney
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
753 ms
Tools exposed
47 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Disney character database MCP.
Listing
From the official MCP registry (active).
Recent checks of Disney
CheckedResultHandshake
1 hour agoHandshake completed753 ms
1 day agoHandshake completed160 ms
2 days agoHandshake completed143 ms
3 days agoHandshake completed146 ms
4 days agoHandshake completed56 ms
5 days agoHandshake completed70 ms
6 days agoHandshake completed110 ms
8 days agoHandshake completed68 ms
11 days agoHandshake completed70 ms
13 days agoHandshake completed74 ms
16 days agoHandshake completed114 ms
18 days agoHandshake completed53 ms
20 days agoHandshake completed98 ms
22 days agoHandshake completed81 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed49 ms
27 days agoHandshake completed69 ms
29 days agoHandshake completed49 ms

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

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 Disney and makes no claim about it beyond what these checks measured.