mcpbeat Sign in

Terlido MCP Server

answering

Terlido is answering right now. Last checked 10 min ago.

Cold email: campaigns, leads, mailboxes, warmup and inbox replies.

Uptime history 4 hours of history
4 hours agonow
100.0%
Uptime 24h
11 of 11 checks
—
Tools
hidden behind auth
392 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

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

run in your terminal
claude mcp add terlido --transport http https://terlido.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "terlido": {
      "url": "https://terlido.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.terlido]
url = "https://terlido.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "terlido": {
      "url": "https://terlido.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "terlido": {
      "url": "https://terlido.com/api/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://terlido.com/api/mcp streamable-http sign-in 399 ms 10 min ago

Alternatives to Terlido

same job, measured the same way
Sendsets
by addisonhoff

Cold email API for AI agents: connect mailboxes, warm up, run campaigns and handle replies.

answering
Warmerly
by warmerly

Cold email outreach: find leads, launch campaigns, fix deliverability, answer replies.

answering
Senders MCP
by dame-senders

Cold email infrastructure — campaigns, prospects, mailbox health and replies via Claude.

answering
Aerosend
by aerosend

Manage Aerosend cold email domains, mailboxes, tags, warmup, inbox placement and domain burn.

answering
Outreach2day
by outreach2day

Cold email infrastructure: domains, mailboxes, warm-up and campaigns. Never charges a card.

24 tools answering
Bavlio
by bavlio

LinkedIn + cold email outreach: find leads, launch personalized campaigns, manage replies.

answering
AI Mail MCP
by aimailmcp

Real email for AI agents: domains, mailboxes, a unified inbox, wait-for-code, send and reply.

answering
Sendraven
by sendraven

Email infrastructure for AI agents: send, read replies as threads, campaigns, per-key limits.

186 installs/wk 55 tools answering

Terlido — questions

Answers built from our own checks of this server.

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