Remote MCP · Endpoint

Polyxd MCP server

No. Polyxd answered an MCP handshake 6 hours ago.

UpLast checked 6 hours 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
213 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
6 hours agoHandshake completed213 ms
2 days agoHandshake completed154 ms
4 days agoHandshake completed151 ms
6 days agoHandshake completed184 ms
8 days agoHandshake completed241 ms
10 days agoHandshake completed66 ms
12 days agoHandshake completed358 ms
13 days agoHandshake completed272 ms
14 days agoHandshake completed442 ms
15 days agoHandshake completed285 ms
18 days agoHandshake completed184 ms
20 days agoHandshake completed171 ms
21 days agoHandshake completed211 ms
23 days agoHandshake completed410 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 Polyxd and makes no claim about it beyond what these checks measured.