mcpbeat Sign in

deploy.social MCP Server

answering

deploy.social is answering right now. Last checked 11 min ago.

Post a video once to YouTube Shorts, Instagram/Facebook Reels, TikTok, Threads, X and Bluesky

Uptime history 13 days of history · worst day 0%
13 days agonow
50.0%
Uptime 24h
91 of 182 checks
—
Tools
hidden behind auth
438 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

deploy.social does not always answer

Over the last week it answered 49.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 11 min ago.

run in your terminal
claude mcp add mcp --transport http https://api.deploy.social/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.deploy.social/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.deploy.social/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.deploy.social/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.deploy.social/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.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Endpoints

URLTransportStateLatencyChecked
https://api.deploy.social/api/mcp streamable-http answering 437 ms 11 min ago
https://api.deploy.social/mcp streamable-http sign-in 437 ms 11 min ago

Alternatives to deploy.social

same job, measured the same way
AppCrane
by gitayg

Deploy and manage apps on your own AppCrane instance, the self-hosted PaaS for AI-built apps.

95 installs/wk local only
OBTO
by obto

Your AI builds, deploys, and runs full-stack apps on a hosted workspace created at first sign-in.

answering
Firebase Deploy Leak Audit
by jmshinhwa

Reads firebase.json and names the files your next firebase deploy would publish to the open web

117 installs/wk local only
Gmail MCP
by mkpoli

Multi-account Gmail on a Cloudflare Worker you deploy yourself: read, send, reply, labels, threads

local only
Croft
by oncroft

Deploy and host the apps your AI assistant builds — a real server, database, and shareable URL.

26 tools answering
Bim
by makata

Design-review threads, comments, reactions and deployments from Bim. Sign in with Google.

answering
InstaPods
by instapods

Deploy and manage web apps on InstaPods: create pods, push files, run commands, read logs.

answering
FlowCastle
by flowcastle

Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform.

57 tools answering

deploy.social — questions

Answers built from our own checks of this server.

Why is there no tool list for deploy.social?
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: 50.0% of checks in the last 24 hours got a reply.
Is deploy.social working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 182 checks got a reply (50.0%), average response time 438 ms. The bar chart above shows every period we have measured.
How do I connect deploy.social?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path 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 deploy.social?
No API key is involved. deploy.social 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 deploy.social?
It answers our handshake in 438 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.