Remote MCP · Endpoint

Dreamwork MCP server

No. Dreamwork answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://mcp.dreamworkhq.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.dreamworkhq/dreamwork
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
37 ms
Tools exposed
74 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Job search, application materials, and application tracking for AI assistants.
Listing
From the official MCP registry (active).
Recent checks of Dreamwork
CheckedResultHandshake
8 hours agoHandshake completed37 ms
3 days agoHandshake completed37 ms
12 days agoHandshake completed60 ms
13 days agoHandshake completed40 ms
14 days agoHandshake completed48 ms
15 days agoHandshake completed37 ms
16 days agoHandshake completed46 ms
17 days agoHandshake completed163 ms
18 days agoHandshake completed35 ms
20 days agoHandshake completed35 ms
22 days agoHandshake completed33 ms
25 days agoHandshake completed133 ms
27 days agoHandshake completed471 ms
30 days agoHandshake completed137 ms

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

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