mcpbeat Sign in

Bereach MCP Server

by benjaminb10 Your server? Claim it
answering

Bereach is answering right now. Last checked moments ago.

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

Uptime history 61 days of history · worst day 90%
61 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
377 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.

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 0 min ago.

run in your terminal
claude mcp add bereach --transport http https://mcp.bereach.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "bereach": {
      "type": "http",
      "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

URLTransportStateLatencyChecked
https://mcp.bereach.ai/mcp streamable-http sign-in 262 ms 0 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.

16 tools answering
GTM Otto
by gtmotto

Self-driving LinkedIn prospecting: it sources, warms and invites daily. You approve every message.

21 tools answering
Famelab: LinkedIn AI agents
by famelab

LinkedIn AI agents for B2B: leads, inbox, draft replies, campaigns and posts. You approve each send.

answering
Gigi AI
by usegigi

LinkedIn outreach from Claude with a human veto: review, approve and send drafts, triage replies.

answering
Linked API
by linked-api

Manage LinkedIn messages, connections, posts, and profile data through Linked API.

652 installs/wk 68 tools answering
Signado MCP
by signado

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

answering
Re:Vault
by re-vault

Find B2B buyers with a live reason to talk, write first messages, send from your own LinkedIn.

answering
Evascrape
by evascrape

Find business leads with emails from Google Maps, Apollo.io and LinkedIn. Prepaid, API key.

114 installs/wk 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 377 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 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 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 377 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.