mcpbeat Sign in

Send MCP Server

not responding

Send is listed as active in the registry but did not answer our last check.

Uptime history 51 days of history · worst day 0%
51 days agonow
2.2%
Uptime 24h
2 of 90 checks
Tools
hidden behind auth
595 ms
Response time
average over 24h
open, no key
Access
streamable-http

Send does not always answer

Over the last week it answered 0.5% 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 14 min ago.

run in your terminal
claude mcp add mcp --transport http https://www.send.co/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://www.send.co/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://www.send.co/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://www.send.co/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://www.send.co/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://www.send.co/mcp streamable-http answering 193 ms 14 min ago

Alternatives to Send

same job, measured the same way
Sentry
by sentry
answering
UTC second
by sadri-dridi

UTC second

30 tools answering
Semrush
by semrush
answering
Clicksend MCP Server
by clicksend

MCP for ClickSend.

76 installs/wk local only
UTC second 0-60 band
by sadri-dridi

UTC second 0-60 band

30 tools answering
UTC second 0-60 band
by sadri-dridi

UTC second 0-60 band

30 tools answering
SemVer shape
by sadri-dridi

SemVer shape

30 tools answering
Sendgrid
by pipeworx-io

SendGrid MCP — wraps SendGrid v3 API (api.sendgrid.com/v3)

answering

Send — questions

Answers built from our own checks of this server.

Is Send working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 2 of 90 checks got a reply (2.2%), average response time 595 ms. The bar chart above shows every period we have measured.
The registry lists Send as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Send?
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.
Does Send need an API key?
No. Send completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How fast is Send?
It answers our handshake in 595 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.