Remote MCP · Endpoint

Polyxd MCP server

No. Polyxd answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.polyxd.com/mcp

The last check completed an MCP handshake.

Registry name
com.polyxd/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
168 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Write Polyxd UI documents, check them, and show them as real screens in any design-system pack.
Listing
From the official MCP registry (active).
Recent checks of Polyxd
CheckedResultHandshake
34 minutes agoHandshake completed168 ms
8 days agoHandshake completed197 ms
9 days agoHandshake completed173 ms
11 days agoHandshake completed192 ms
12 days agoHandshake completed290 ms
12 days agoHandshake completed464 ms
14 days agoHandshake completed365 ms
14 days agoHandshake completed328 ms
16 days agoHandshake completed492 ms
19 days agoHandshake completed183 ms
21 days agoHandshake completed200 ms
24 days agoHandshake completed213 ms
26 days agoHandshake completed154 ms
28 days agoHandshake completed151 ms

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

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