mcpbeat Sign in

Send MCP Server

by send Your server? Claim it
answering

Send is answering right now. Last checked 14 min ago.

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

Nothing serious here today

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

run in your terminal
claude mcp add mcp --transport http https://www.send.co/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://www.send.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://www.send.co/mcp streamable-http sign-in 291 ms 14 min ago

Alternatives to Send

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

UTC second

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

MCP for ClickSend.

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

UTC second 0-60 band

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

UTC second 0-60 band

31 tools answering
SemVer shape
by sadri-dridi

SemVer shape

31 tools answering
Sendgrid
by pipeworx-io

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

327 installs/wk 47 tools answering

Send — questions

Answers built from our own checks of this server.

Why is there no tool list for Send?
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 Send working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 358 ms. The bar chart above shows every period we have measured.
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 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 Send?
No API key is involved. Send 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 Send?
It answers our handshake in 358 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.