Remote MCP · Endpoint

Shorti MCP server

No. Shorti answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://shorti.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.shorti/shorti
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
615 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
What short-form formats to shoot this week, how their hits were made, and a check of your take.
Listing
From the official MCP registry (active).
Recent checks of Shorti
CheckedResultHandshake
1 hour agoHandshake completed615 ms
2 days agoHandshake completed716 ms
4 days agoHandshake completed648 ms
6 days agoHandshake completed757 ms
8 days agoHandshake completed671 ms
10 days agoHandshake completed647 ms
12 days agoHandshake completed763 ms
14 days agoHandshake completed657 ms
15 days agoHandshake completed665 ms
16 days agoHandshake completed613 ms
18 days agoHandshake completed604 ms
20 days agoHandshake completed595 ms
22 days agoHandshake completed604 ms
24 days agoHandshake completed608 ms
25 days agoHandshake completed733 ms

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

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