Remote MCP · Endpoint

uplika MCP server

No. uplika answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://api.uplika.com/mcp

The last check completed an MCP handshake.

Registry name
com.uplika/uplika
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
254 ms
Tools exposed
65 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Your AI agent publishes to Threads, Instagram, YouTube and the other social channels you connect.
Listing
From the official MCP registry (active).
Recent checks of uplika
CheckedResultHandshake
7 hours agoHandshake completed254 ms
2 days agoHandshake completed256 ms
4 days agoHandshake completed220 ms
5 days agoHandshake completed252 ms
7 days agoHandshake completed903 ms
8 days agoHandshake completed837 ms
9 days agoHandshake completed248 ms
12 days agoHandshake completed831 ms
13 days agoHandshake completed245 ms
15 days agoHandshake completed260 ms
16 days agoHandshake completed244 ms
17 days agoHandshake completed233 ms
19 days agoHandshake completed242 ms
19 days agoHandshake completed252 ms
20 days agoHandshake completed238 ms
21 days agoHandshake completed2.67 s
22 days agoHandshake completed796 ms

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

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