Remote MCP · Endpoint

Instoryview MCP server

No. Instoryview answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://instoryview.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.instoryview/instoryview
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
384 ms
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Instagram profiles, follower/following snapshots and changes, with budgeted public lookups.
Listing
From the official MCP registry (active).
Recent checks of Instoryview
CheckedResultHandshake
1 hour agoHandshake completed384 ms
3 days agoHandshake completed401 ms
12 days agoHandshake completed415 ms
13 days agoHandshake completed384 ms
15 days agoHandshake completed472 ms
15 days agoFailed - the request timed out—
17 days agoHandshake completed385 ms
18 days agoHandshake completed380 ms
18 days agoHandshake completed372 ms
20 days agoHandshake completed1.04 s
22 days agoHandshake completed379 ms
25 days agoHandshake completed383 ms
27 days agoHandshake completed442 ms
29 days agoHandshake completed438 ms

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

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