Remote MCP · Endpoint

instapi: Instagram MCP server

No. instapi: Instagram answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://instapi.co/mcp

The last check completed an MCP handshake.

Registry name
co.instapi/instagram
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
118 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Instagram search and posts for AI agents, with images and videos AI-parsed to text.
Listing
From the official MCP registry (active).
Recent checks of instapi: Instagram
CheckedResultHandshake
1 hour agoHandshake completed118 ms
2 days agoHandshake completed4.74 s
5 days agoHandshake completed6.97 s
7 days agoHandshake completed430 ms
9 days agoHandshake completed161 ms
11 days agoHandshake completed538 ms
13 days agoHandshake completed103 ms
15 days agoHandshake completed55 ms
17 days agoHandshake completed160 ms
18 days agoHandshake completed69 ms
19 days agoHandshake completed591 ms
20 days agoHandshake completed88 ms
23 days agoHandshake completed63 ms
24 days agoHandshake completed144 ms

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