Remote MCP · Endpoint

Frontic UI MCP server

No. Frontic UI answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://mcp.ui.frontic.com/mcp

The last check completed an MCP handshake.

Registry name
com.frontic/ui
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
227 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search, read and add Frontic UI's Vue components for commerce storefronts.
Listing
From the official MCP registry (active).
Recent checks of Frontic UI
CheckedResultHandshake
44 minutes agoHandshake completed227 ms
3 days agoHandshake completed263 ms
12 days agoHandshake completed335 ms
13 days agoHandshake completed400 ms
14 days agoHandshake completed323 ms
15 days agoHandshake completed356 ms
16 days agoHandshake completed274 ms
17 days agoHandshake completed348 ms
18 days agoHandshake completed274 ms
19 days agoHandshake completed349 ms
22 days agoHandshake completed282 ms
25 days agoHandshake completed260 ms
27 days agoHandshake completed306 ms

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

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