Remote MCP · Endpoint

AutoShort MCP server

No. AutoShort answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://autoshort.org/api/mcp

The last check completed an MCP handshake.

Registry name
org.autoshort/autoshort
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
207 ms
Tools exposed
55 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Make faceless AI short videos from a topic, product page or image: script, voiceover, captions.
Listing
From the official MCP registry (active).
Recent checks of AutoShort
CheckedResultHandshake
13 minutes agoHandshake completed207 ms
9 days agoHandshake completed219 ms
9 days agoHandshake completed222 ms
11 days agoHandshake completed234 ms
12 days agoHandshake completed207 ms
13 days agoHandshake completed221 ms
14 days agoHandshake completed212 ms
15 days agoCredentials required—
16 days agoCredentials required—
19 days agoCredentials required—
21 days agoCredentials required—
24 days agoCredentials required—
26 days agoCredentials required—
28 days agoCredentials required—

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