Remote MCP · Endpoint

PromptUI MCP server

No. PromptUI answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://www.promptui.co/api/mcp

The last check completed an MCP handshake.

Registry name
co.promptui/promptui
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
119 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Build a working web app from a prompt, then deploy it to a live URL.
Listing
From the official MCP registry (active).
Recent checks of PromptUI
CheckedResultHandshake
9 hours agoHandshake completed119 ms
2 days agoHandshake completed1.55 s
4 days agoHandshake completed101 ms
5 days agoHandshake completed127 ms
7 days agoHandshake completed103 ms
8 days agoHandshake completed172 ms
9 days agoHandshake completed116 ms
12 days agoHandshake completed85 ms
14 days agoHandshake completed96 ms
15 days agoHandshake completed111 ms
16 days agoHandshake completed212 ms
18 days agoHandshake completed151 ms
19 days agoHandshake completed103 ms
19 days agoHandshake completed171 ms
20 days agoHandshake completed1.68 s
21 days agoHandshake completed135 ms
23 days agoHandshake completed99 ms

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

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