Remote MCP · Endpoint

Clippy Mc Clipface MCP server

No. Clippy Mc Clipface answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://getclippy.co/mcp

The last check completed an MCP handshake.

Registry name
co.getclippy/clippy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
283 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free, read-only coupon code lookup for your AI. Affiliate: Clippy may earn a commission.
Listing
From the official MCP registry (active).
Recent checks of Clippy Mc Clipface
CheckedResultHandshake
1 hour agoHandshake completed283 ms
2 days agoHandshake completed198 ms
5 days agoHandshake completed187 ms
7 days agoHandshake completed220 ms
9 days agoHandshake completed176 ms
11 days agoHandshake completed205 ms
13 days agoHandshake completed196 ms
15 days agoHandshake completed212 ms
17 days agoHandshake completed268 ms
19 days agoHandshake completed390 ms
20 days agoHandshake completed201 ms
21 days agoHandshake completed201 ms
22 days agoHandshake completed195 ms
25 days agoHandshake completed216 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 Clippy Mc Clipface and makes no claim about it beyond what these checks measured.