Remote MCP · Endpoint

Shorti MCP server

No. Shorti answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes 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
679 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 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.
Website
https://shorti.ai/
Listing
From the official MCP registry (active).
Recent checks of Shorti
CheckedResultHandshake
34 minutes agoHandshake completed679 ms
8 days agoHandshake completed652 ms
9 days agoHandshake completed686 ms
11 days agoHandshake completed691 ms
12 days agoHandshake completed701 ms
12 days agoHandshake completed818 ms
14 days agoHandshake completed682 ms
14 days agoHandshake completed326 ms
16 days agoHandshake completed705 ms
19 days agoHandshake completed760 ms
21 days agoHandshake completed615 ms
24 days agoHandshake completed716 ms
26 days agoHandshake completed648 ms
28 days agoHandshake completed757 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.