Remote MCP · Endpoint

getwowlink MCP server

No. getwowlink answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.getwowlink.com/

The last check completed an MCP handshake.

Registry name
com.getwowlink/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
87 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check link previews (Open Graph, Twitter cards) on X, LinkedIn, Slack; OG images per page.
Listing
From the official MCP registry (active).
Recent checks of getwowlink
CheckedResultHandshake
2 hours agoHandshake completed87 ms
20 hours agoHandshake completed97 ms
1 day agoHandshake completed133 ms
2 days agoHandshake completed133 ms
4 days agoHandshake completed589 ms
7 days agoHandshake completed78 ms
9 days agoHandshake completed558 ms
12 days agoHandshake completed93 ms
14 days agoHandshake completed100 ms
16 days agoHandshake completed96 ms
18 days agoHandshake completed90 ms
20 days agoHandshake completed101 ms
22 days agoHandshake completed77 ms
23 days agoHandshake completed83 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 getwowlink and makes no claim about it beyond what these checks measured.