mcpbeat Sign in

Quibbly MCP Server

answering

Quibbly is answering right now. Last checked 1 min ago.

Your LinkedIn inbox, connections and video views for AI. Works with any CRM. Drafts only.

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

Nothing serious here today

Today is the operative word: we check Quibbly 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 1 min ago.

run in your terminal
claude mcp add linkedin-inbox --transport http https://server.quibbly.co/mcp
Settings → Connectors → Add custom connector, then paste this address
https://server.quibbly.co/mcp
~/.codex/config.toml
[mcp_servers.linkedin-inbox]
url = "https://server.quibbly.co/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "linkedin-inbox": {
      "url": "https://server.quibbly.co/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "linkedin-inbox": {
      "type": "http",
      "url": "https://server.quibbly.co/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://server.quibbly.co/mcp streamable-http sign-in 377 ms 1 min ago

Alternatives to Quibbly

same job, measured the same way
LeadDelta MCP Server
by leaddelta

MCP server for LeadDelta — manage LinkedIn connections and CRM data via AI assistants.

answering
ego
by ego

Write LinkedIn posts in your own voice. Drafts only, ego never publishes for you.

answering
Profile-Wrap
by nj-burrito

Draft, gate and review LinkedIn posts in a Profile-Wrap workspace; posts only board-Allowed drafts.

484 installs/wk local only
Famelab: LinkedIn AI agents
by famelab

LinkedIn AI agents for B2B: leads, inbox, draft replies, campaigns and posts. You approve each send.

answering
OutreachGenie Workspace
by outreachgenie

LinkedIn prospecting for AI agents: lists, outreach flows, and campaigns in OutreachGenie.

answering
Emelia
by emelia

Run Emelia cold email and LinkedIn campaigns, lists, enrichment and your Emelia inbox from AI.

answering
LeadShark Apex: LinkedIn MCP
by leadshark

LinkedIn MCP with 47 tools: post, comment, DM and run comment-to-DM automations inside your limits.

answering
Linkedin
by reachium

LinkedIn campaigns, content, leads and inbox from your AI client. Scoped, revocable keys.

answering

Quibbly — questions

Answers built from our own checks of this server.

Why is there no tool list for Quibbly?
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 Quibbly 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 394 ms. The bar chart above shows every period we have measured.
How do I connect Quibbly?
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 Quibbly?
No API key is involved. Quibbly 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 Quibbly?
It answers our handshake in 394 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.