Vendor: versium.com · entry id 01-versium-reach · source 01-data-enrichment.md line 579
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 by hand on 2026-08-25. On 2026-09-04 the recorded URL answered an MCP initialize as a server, which is liveness and nothing more: nobody has run its tools.
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/)
Not harvested yet. Unmeasured, not empty: nobody has read this server's tool list, so this page says nothing about what it exposes.
141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. The full roll up is on the tools index.
No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.
api_gate, verbatim from the file:
paid
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.
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.
github.com/VersiumAnalytics tied to the vendor by rule 3, account website https://versium.com has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| reach-api-sdk-node | SDK | Node.js client library for accessing the Versium REACH API | 5 | 2025-10-01 | v1.1.1 |
| offline-file-hasher | other | This javascript hashes a file on your computer, then saves the hashed output. This process is 100% offline and... | 2 | 2023-07-14 | |
| reach-api-php-sdk | SDK | A PHP client library for accessing the REACH APIs | 1 | 2023-06-21 | v0.4.0 |
| reach-api-python-sdk | SDK | 3 | 2023-05-24 | v1.1.0 | |
| versium-modeling | other | Tools for appending data and creating lead scoring models | 5 | 2022-10-06 | v0.1.0 |
Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.
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 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.
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
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.