Remote MCP · Endpoint

Shortimize MCP server

No. Shortimize answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.shortimize.com/mcp

The last check completed an MCP handshake.

Registry name
com.shortimize/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
84 ms
Tools exposed
32 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Track TikTok, Instagram Reels and YouTube Shorts accounts and videos: views, growth and analytics.
Listing
From the official MCP registry (active).
Recent checks of Shortimize
CheckedResultHandshake
1 hour agoHandshake completed84 ms
19 hours agoHandshake completed63 ms
2 days agoHandshake completed32 ms
3 days agoHandshake completed28 ms
4 days agoHandshake completed50 ms
5 days agoHandshake completed68 ms
6 days agoHandshake completed96 ms
8 days agoHandshake completed378 ms
10 days agoHandshake completed48 ms
13 days agoHandshake completed189 ms
15 days agoHandshake completed64 ms
17 days agoHandshake completed42 ms
19 days agoHandshake completed37 ms
21 days agoHandshake completed65 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 Shortimize and makes no claim about it beyond what these checks measured.