mcpbeat

My MCP Serv MCP Server

live.alpic.staging.send-email-mcp-04d3fdca/send-email-mcp
answering

My MCP Serv is answering right now. Last checked 10 min ago. It exposes 1 tools.

Non functional server (yet)

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
696 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

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

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

send
send_email
Send an email via Resend API. Args: sender_email: Sender email address (must be verified in Resend) to_emails: List of recipient email addresses subject: Email subject line text_content: Plain text content (required if html_content not provided) html_content: HTML content (required if text_content not provided) Returns: API response with email ID on success

Endpoints

URLTransportStateLatencyChecked
https://send-email-mcp-04d3fdca.staging.alpic.live streamable-http answering 502 ms 10 min ago

My MCP Serv — questions

Answers built from our own checks of this server.

What can My MCP Serv do?
It exposes 1 tools, read directly from the server on our last check. Among them: send_email. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is My MCP Serv 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 696 ms. The bar chart above shows every period we have measured.
How do I connect My MCP Serv?
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 My MCP Serv need an API key?
No. My MCP Serv completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is My MCP Serv?
It answers our handshake in 696 ms on average, which is faster than 12% 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.