The GTM MCP Directory
Directory / Data & Enrichment / Versium REACH

Versium REACH

Official MCP Paid, self-serve Data & Enrichment RESEARCHED Checked 2026-08-25
RESEARCHED Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 0.

Vendor: versium.com · entry id 01-versium-reach · source 01-data-enrichment.md line 579

What it does
An identity-graph append service that turns partial contact records into enriched B2B and B2C profiles, plus audience sizing and real-time email validation.
AI features, separated from automation with an AI label on it
The MCP layer translates natural language into REACH API calls. The underlying identity resolution is deterministic graph matching, not AI. This is a clean example of an "AI" surface bolted onto a non-AI core, and the entry says so.
RevOps role
Identity resolution and append step between raw lead capture and CRM or ad-platform activation.
MCP server
Status bucket
Official MCP
Auth
OAuth, and the client must support dynamic client registration.
Parsed URLs
3 found in the mcp_url field

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-08-25 and has not been re-fetched since.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://app.versium.com/mcp/reach (docs: https://reach-help.versium.com/docs/mcp-overview; announcement: https://versium.com/blog/versium-launches-versium-reach-mcp-server/)

Access gate
Gate bucket
Paid, self-serve
Can a solo operator reach it
Yes, by paying, no sales call

api_gate, verbatim from the file:

paid

API documentation

https://reach-help.versium.com/docs/mcp-overview

No documentation text is reproduced anywhere on this site. Read the vendor page for the prose. The structured docs digest specced in SPEC section 3 has not been built or crawled: docs_digest is null on every entry in this build.

GitHub health

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

Jobs it can do

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total.

Sources

4 source URLs. Raw sources field, verbatim:

https://versium.com/blog/versium-launches-versium-reach-mcp-server/, https://versium.com/versium-reach-mcp/, https://reach-help.versium.com/docs/mcp-overview, https://www.pulsemcp.com/servers/versium-reach

Notes, verbatim from the file
Added 2026-08-25 in the coverage sweep. Launched February 2026. Tool surface covers contact, demographic and firmographic appends, C2B and IP-to-domain resolution, a consumer audience builder, B2B list estimates, and email hygiene. Requires an existing REACH account, so a solo operator needs a paid seat before the MCP is usable. The dynamic-client-registration requirement is a real compatibility constraint: clients that do not implement DCR cannot connect at all.
Provenance
Entry id
01-versium-reach
Source file
01-data-enrichment.md
Source line
579
Tier
RESEARCHED
last_checked
2026-08-25
Data baked
2026-08-25

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.