mcpbeat Sign in

SocialListeningAPI MCP Server

by sociallisteningapi Your server? Claim it
answering

SocialListeningAPI is answering right now. Last checked 3 min ago.

Search public social posts and web results from AI assistants.

Uptime history 90 days of history · worst day 99%
90 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
239 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check SocialListeningAPI every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add social-listening --transport http https://api.sociallisteningapi.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.sociallisteningapi.com/mcp
~/.codex/config.toml
[mcp_servers.social-listening]
url = "https://api.sociallisteningapi.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "social-listening": {
      "url": "https://api.sociallisteningapi.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "social-listening": {
      "type": "http",
      "url": "https://api.sociallisteningapi.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.sociallisteningapi.com/mcp streamable-http sign-in 260 ms 3 min ago

Alternatives to SocialListeningAPI

same job, measured the same way
Threads by 1Social
by 1social

Publish and schedule Threads posts from your AI assistant.

answering
PostDovo
by postdovo

Draft, schedule and publish social media posts from your AI assistant.

answering
LinkedIn by 1Social
by 1social

Publish and schedule LinkedIn posts from your AI assistant.

answering
Facebook by 1Social
by 1social

Publish and schedule Facebook Page posts from your AI assistant.

answering
Bluesky by 1Social
by 1social

Publish and schedule Bluesky posts and threads from your AI assistant.

answering
Instagram by 1Social
by 1social

Publish and schedule Instagram posts, Reels and carousels from your AI assistant.

answering
Keryo
by keryo

Create, schedule, and publish social media posts from AI assistants. Built for agencies.

answering
TikTok by 1Social
by 1social

Publish and schedule TikTok videos and photo posts from your AI assistant.

answering

SocialListeningAPI — questions

Answers built from our own checks of this server.

Why is there no tool list for SocialListeningAPI?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is SocialListeningAPI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 239 ms. The bar chart above shows every period we have measured.
How do I connect SocialListeningAPI?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to SocialListeningAPI?
No API key is involved. SocialListeningAPI answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is SocialListeningAPI?
It answers our handshake in 239 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.