Vendor: vayne.io · entry id 01-vayne · source 01-data-enrichment.md line 853
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-09-07 and the MCP URL has not been probed live yet.
mcp_status, verbatim from the file:
official
mcp_url, verbatim from the file:
https://mcp.vayne.io/mcp (docs: https://www.vayne.io/en/mcp-documentation)
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.
Install, as the source shows it:
npm install -g @vayne/cliquoted from https://www.npmjs.com/package/@vayne/cli on 2026-09-27, via npm
Packages seen, with the version on 2026-09-27:
A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.
api_gate, verbatim from the file:
paid - the vendor's MCP documentation states "Using the MCP requires a plan with API access (Starter and above), OAuth connections included: on a lower plan the connector still authorizes, but every tool call comes back with 'Plan does not include API access'." Starter is $49/month or $490/year on the published pricing page; a Free plan (200 leads/month) and a $29/month Freelance plan sit below it and do not carry API access.
No documentation URL recorded.
727 of 1252 entries are in the same position. Blank is legal and it is published as blank.
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.
No GitHub organisation could be tied to vayne.io with evidence on 2026-09-08.
Recorded by the harvest: github candidates were seen but none passed the evidence rules.
5 candidate accounts seen and rejected by the evidence rules: VaynerMedia-NewYork, vaynerx, VaynerMedia-London, vaynejs, vaynermedia. A name match alone is never accepted; the account has to point at the vendor domain.
No job tag on this entry.
981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag.
3 source URLs. Raw sources field, verbatim:
https://www.vayne.io/en/mcp-documentation, https://www.vayne.io/en/pricing, https://mcp.vayne.io/mcp
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.