mcpbeat Sign in

mySDR MCP Server

answering

mySDR is answering right now. Last checked 1 min ago.

GTM execution layer for AI agents: buyer signals, enrichment and approved LinkedIn outreach over MCP

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

Nothing serious here today

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

run in your terminal
claude mcp add assistant --transport http https://mysdr.app/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mysdr.app/api/mcp
~/.codex/config.toml
[mcp_servers.assistant]
url = "https://mysdr.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "assistant": {
      "url": "https://mysdr.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "assistant": {
      "type": "http",
      "url": "https://mysdr.app/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://mysdr.app/api/mcp streamable-http sign-in 209 ms 1 min ago

Alternatives to mySDR

same job, measured the same way
gtm-api: LinkedIn MCP Server
by gtm-api

Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own.

358 installs/wk answering
Kairon
by heykairon

Build prospecting lists from buying signals, enrich them, and run LinkedIn outreach.

answering
Sumora
by trysumora

Shopify for AI agents. Run Sumora's approval-first LinkedIn and Instagram outreach agent.

answering
Fintalio LinkedIn MCP
by fintalio

LinkedIn outreach MCP server — 19 tools for AI agents to prospect, sequence, and manage contacts.

answering
PumpGTM MCP server
by pumpgtm

Find buyers, run LinkedIn, email and X outreach, and answer replies from your AI.

answering
Linkedin Outreach MCP
by csoai-org

Linkedin Outreach MCP Server by MEOK AI Labs

144 installs/wk local only
Marvenn MCP Server
by marvennai

Connect AI agents to Marvenn for outbound growth via email, voice, and LinkedIn.

52 installs/wk local only
Signado MCP
by signado

LinkedIn warm-lead discovery: list leads, find emails, and draft outreach from your AI tools.

answering

mySDR — questions

Answers built from our own checks of this server.

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