Skip to content
External endpointresponds

socialclaw

Connect any AI agent to 11+ social platforms: schedule, publish & track posts via hosted MCP.

Endpoint URL
https://getsocialclaw.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:01 AM UTC
Check
MCP initialize · 8s limit
Latency
320 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.ndesv21/socialclaw

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
socialclaw
Version
0.1.15
Capability keys
tools
Tool names
list_accounts, account_capabilities, connect_account, upload_asset, validate_schedule, preview_campaign, apply_schedule, publish_draft, list_posts, list_assets, get_post, post_attempts, retry_post, cancel_post, run_status, get_analytics, list_instagram_media, get_instagram_comments, reply_instagram_comment, hide_instagram_comment, delete_instagram_comment, get_instagram_media_insights, get_instagram_profile, get_instagram_account_insights, react_instagram_message, list_instagram_mentions, list_instagram_conversations, get_instagram_messages, send_instagram_message, workspace_usage, workspace_health
Instructions excerpt

SocialClaw publishes social media posts through connected workspace accounts on X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, and Pinterest. Authenticate with `Authorization: Bearer <workspace API key>` from https://getsocialclaw.com/dashboard. Typical flow: list_accounts -> account_capabilities -> (list_assets to reuse an already-uploaded file, or upload_asset for a new one) -> validate_schedule -> apply_schedule -> run_status. To post media the user uploaded in the dashboard, call list_assets and use an asset's publicUrl as media_link.

Reported Aug 17, 2026, 05:01 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 199ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 532ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 319ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 320ms
Back to MCP directory