Remote MCP · Endpoint

McClipFace MCP server

No. McClipFace answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcclipface.com/mcp

The last check completed an MCP handshake.

Registry name
co.getclippy/clippy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
192 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
McClipFace finds current coupon codes, promo codes, deals and discounts for stores and products.
Listing
From the official MCP registry (active).
Recent checks of McClipFace
CheckedResultHandshake
1 hour agoHandshake completed192 ms
1 day agoHandshake completed222 ms
4 days agoHandshake completed271 ms
6 days agoHandshake completed431 ms
9 days agoHandshake completed240 ms
11 days agoHandshake completed290 ms
13 days agoHandshake completed197 ms
15 days agoHandshake completed183 ms
17 days agoHandshake completed196 ms
19 days agoHandshake completed191 ms
21 days agoHandshake completed207 ms
22 days agoHandshake completed189 ms
24 days agoHandshake completed193 ms
25 days agoHandshake completed188 ms
27 days agoHandshake completed198 ms

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

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