Bereach

io.github.benjaminb10Published by GitHub account benjaminb10v1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant find, qualify and message B2B leads from public LinkedIn data, with every send requiring human approval.

What you can do
Bereach is a remote MCP server that lets an assistant work with B2B lead generation: finding and qualifying prospects from public LinkedIn data, and preparing outreach messages. Every message send is gated by human approval rather than going out automatically. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to help build and qualify a B2B prospect list from public LinkedIn data and draft outreach, while keeping a person in the loop before anything is sent.
Requirements
A remote MCP endpoint at mcp.bereach.ai over streamable HTTP. Authentication is OAuth and is required; no environment variables or headers are declared. A Bereach account is implied by the OAuth sign-in.
Before you install
The server handles prospect data and outreach messaging, so review what is sent to the service. Sends are described as human-approved, but confirm that approval step is enforced before relying on it. OAuth grants access to your Bereach account; review the scopes requested.

Installation

In SourceWeft

  1. Open Bereach in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.benjaminb10%2Fbereach/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.