Remote MCP · Endpoint

HasData Instagram MCP server

No. HasData Instagram answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://mcp.hasdata.com/api/mcp?apis=instagram

The last check completed an MCP handshake.

Registry name
com.hasdata/instagram
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
45 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Public Instagram profiles and post feeds by handle, with hashtags and mentions parsed.
Listing
From the official MCP registry (active).
Recent checks of HasData Instagram
CheckedResultHandshake
2 days agoHandshake completed45 ms
4 days agoHandshake completed91 ms
5 days agoHandshake completed432 ms
7 days agoHandshake completed151 ms
8 days agoHandshake completed898 ms
9 days agoHandshake completed826 ms
12 days agoCredentials required—
13 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
18 days agoCredentials required—
19 days agoCredentials required—
20 days agoCredentials required—
20 days agoCredentials required—
21 days agoCredentials required—
23 days agoCredentials required—

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