Versium REACH

com.versiumPublished by versium.comOfficial publisherv1.0.0Updated Oct 26, 2026

Enrich leads, generate prospect lists, and validate emails using Versium's B2B2C identity graph.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Versium REACH lets an assistant enrich leads, build prospect lists and validate emails using Versium's B2B2C identity graph, via a hosted remote endpoint.

What you can do
  • Enrich leads with identity and contact data from Versium's B2B2C identity graph
  • Generate prospect lists for outreach and targeting
  • Validate email addresses
  • No individual tools are documented in the supplied listing, so exact operations are not described.
When to use it
Useful when a sales, marketing or data team wants an assistant to enrich contact records, assemble prospect lists or check email validity without leaving the chat workflow.
Requirements
A remote MCP endpoint at app.versium.com over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared. A Versium account is implied by the OAuth sign-in.
Before you install
Requires OAuth sign-in to a Versium account, and usage may be tied to a paid Versium subscription or credits. Lead and contact data is sent to Versium for enrichment, so consider privacy and consent obligations for personal data. Generated lists and validation results should be checked before use.

Installation

In SourceWeft

  1. Open Versium REACH 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/com.versium%2FREACH/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": {
    "versium-reach": {
      "type": "http",
      "url": "https://app.versium.com/mcp/reach"
    }
  }
}

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.