Bereach MCP Server

by benjaminb10 Your server? Claim it

answering

Bereach is answering right now. Last checked 2 min ago.

Find, qualify and message B2B leads from public LinkedIn data; every send is human-approved.

Uptime history 15 days of history

15 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

719 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Bereach every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add bereach --transport http https://mcp.bereach.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "bereach": {
      "url": "https://mcp.bereach.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.bereach]
url = "https://mcp.bereach.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "bereach": {
      "url": "https://mcp.bereach.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "bereach": {
      "url": "https://mcp.bereach.ai/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

URL	Transport	State	Latency	Checked
https://mcp.bereach.ai/mcp	streamable-http	sign-in	583 ms	2 min ago

Alternatives to Bereach

same job, measured the same way

Onsa

by onsa

Find scored B2B leads, read campaign replies and send approved LinkedIn outreach.

13 tools answering

Signado MCP

by signado

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

answering

LinkedIn MCP Server

by com-mcp

LinkedIn API as MCP tools to retrieve profile data and publish content. Powered by HAPI MCP.

3 tools answering

Hilead

by hilead

Signal-based B2B prospecting: find leads with buying intent, run email and LinkedIn outreach.

answering

LinkedNav

by linglistack

Run LinkedIn outreach from your AI chat: find leads, launch campaigns, send, and reply.

answering

Iridium

by iridiumhqmcp

LinkedIn outreach, commenting, scheduling, and data via Claude and human approval gates.

answering

SalesTouch

by salestouch

Give AI agents the LinkedIn tools to find, qualify, engage, and follow up with prospects.

answering

MCP Ethical Hacking

by cmpxchg16

An MCP server that provides LinkedIn & Reddit data

local only

Bereach — questions

Answers built from our own checks of this server.

Why is there no tool list for Bereach?

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 Bereach working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 719 ms. The bar chart above shows every period we have measured.

How do I connect Bereach?

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 Bereach?

No API key is involved. Bereach 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 Bereach?

It answers our handshake in 719 ms on average, which is faster than 16% 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.