Remote MCP · Endpoint

Pagecuts MCP server

No. Pagecuts answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://pagecuts.com/mcp

The last check completed an MCP handshake.

Registry name
com.pagecuts/pagecuts
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
66 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Make a 15-second video ad, still images and ad copy from any web page. US$19 once per kit.
Listing
From the official MCP registry (active).
Recent checks of Pagecuts
CheckedResultHandshake
37 minutes agoHandshake completed66 ms
4 days agoHandshake completed434 ms
7 days agoHandshake completed71 ms
16 days agoHandshake completed371 ms
16 days agoHandshake completed89 ms
18 days agoHandshake completed75 ms
19 days agoHandshake completed121 ms
20 days agoHandshake completed119 ms
21 days agoHandshake completed68 ms
22 days agoHandshake completed115 ms
23 days agoHandshake completed144 ms
26 days agoHandshake completed83 ms
29 days agoHandshake completed108 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 Pagecuts and makes no claim about it beyond what these checks measured.