Remote MCP · Endpoint

com.dropwatchhq/phoenix-screen MCP server

No. com.dropwatchhq/phoenix-screen answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://phoenix.dropwatchhq.com/mcp

The last check completed an MCP handshake.

Registry name
com.dropwatchhq/phoenix-screen
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
82 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Phoenix/rebrand relink detection: links a debarred principal to a newly-formed business entity.
Listing
From the official MCP registry (active).
Recent checks of com.dropwatchhq/phoenix-screen
CheckedResultHandshake
1 hour agoHandshake completed82 ms
18 hours agoHandshake completed67 ms
2 days agoHandshake completed95 ms
3 days agoHandshake completed57 ms
4 days agoHandshake completed44 ms
5 days agoHandshake completed504 ms
6 days agoHandshake completed78 ms
7 days agoHandshake completed127 ms
10 days agoHandshake completed65 ms
13 days agoHandshake completed206 ms
15 days agoHandshake completed61 ms
17 days agoHandshake completed68 ms
19 days agoHandshake completed41 ms
21 days agoHandshake completed44 ms
23 days agoHandshake completed78 ms
25 days agoHandshake completed40 ms
27 days agoHandshake completed97 ms
28 days agoHandshake completed52 ms
29 days agoHandshake completed263 ms

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

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 com.dropwatchhq/phoenix-screen and makes no claim about it beyond what these checks measured.