Remote MCP · Endpoint

Storyflo MCP server

No. Storyflo answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://api.storyflo.com/mcp/v1

The last check completed an MCP handshake.

Registry name
io.github.Alisammour/storyflo-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
27 ms
Tools exposed
37 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Curated audio news, daily briefings, the Declassified library + market-linked signals.
Listing
From the official MCP registry (active).
Recent checks of Storyflo
CheckedResultHandshake
2 days agoHandshake completed27 ms
4 days agoHandshake completed28 ms
5 days agoHandshake completed25 ms
7 days agoHandshake completed174 ms
8 days agoHandshake completed36 ms
9 days agoHandshake completed29 ms
12 days agoHandshake completed28 ms
13 days agoHandshake completed30 ms
15 days agoHandshake completed49 ms
16 days agoHandshake completed247 ms
17 days agoHandshake completed39 ms
19 days agoHandshake completed29 ms
20 days agoHandshake completed30 ms
20 days agoHandshake completed26 ms
21 days agoHandshake completed25 ms
22 days agoHandshake completed37 ms

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

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