Remote MCP · Endpoint

SocialAPIs MCP server

No. SocialAPIs answered an MCP handshake 46 minutes ago.

UpLast checked 46 minutes ago

Server URL

https://mcp.socialapis.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.SocialAPIsHub/social-media-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
529 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Facebook & Instagram data for AI agents: pages, posts, groups, ads, Marketplace, profiles, reels.
Listing
From the official MCP registry (active).
Recent checks of SocialAPIs
CheckedResultHandshake
46 minutes agoHandshake completed529 ms
3 days agoHandshake completed519 ms
13 days agoHandshake completed593 ms
13 days agoHandshake completed547 ms
15 days agoHandshake completed535 ms
16 days agoHandshake completed630 ms
17 days agoHandshake completed523 ms
18 days agoHandshake completed542 ms
18 days agoHandshake completed536 ms
20 days agoHandshake completed514 ms
22 days agoHandshake completed567 ms
25 days agoHandshake completed551 ms
27 days agoHandshake completed419 ms
30 days agoHandshake completed404 ms

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

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