Remote MCP · Endpoint

Unstuck MCP server

No. Unstuck answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://unstuckapi.com/mcp

The last check completed an MCP handshake.

Registry name
com.unstuckapi/unstuck
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
63 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Web search, read any page, verify or find emails, screenshots, keyword data. One key, pay per call.
Listing
From the official MCP registry (active).
Recent checks of Unstuck
CheckedResultHandshake
7 hours agoHandshake completed63 ms
4 days agoHandshake completed79 ms
14 days agoHandshake completed66 ms
15 days agoHandshake completed67 ms
15 days agoHandshake completed98 ms
17 days agoHandshake completed63 ms
18 days agoHandshake completed97 ms
19 days agoHandshake completed95 ms
20 days agoHandshake completed75 ms
21 days agoHandshake completed66 ms
23 days agoHandshake completed120 ms
26 days agoHandshake completed69 ms
28 days agoHandshake completed72 ms

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

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