# Vayne
ID: 01-vayne
Page: https://gtmmcps.com/tools/01-vayne
JSON: https://gtmmcps.com/data/tools/01-vayne.json
Documentation references: https://gtmmcps.com/docs/01-vayne/
Category: Data & Enrichment
MCP support: official
Testing: RESEARCHED
API access: paid
Last checked: 2026-09-07
Endpoint check: not-probed; date: Not recorded

A LinkedIn data platform that runs Sales Navigator lead and account scraping, single-URL and batch profile and company scraping, job scraping and job search, post-engagement scraping, reverse email to LinkedIn lookup, and email and phone enrichment, all of it exposed as MCP tools as well as a REST API.

## MCP links
- https://mcp.vayne.io/mcp
- https://www.vayne.io/en/mcp-documentation

## Sources
- https://www.vayne.io/en/mcp-documentation
- https://www.vayne.io/en/pricing
- https://mcp.vayne.io/mcp

## Research notes
Verified 2026-09-07: POST of an MCP initialize to https://mcp.vayne.io/mcp returned HTTP 401 with a JSON-RPC error reading "Missing or invalid Authorization header. Provide your Vayne API token (or an OAuth access token) as a Bearer token.", which confirms a live auth-gated server and confirms both auth paths in one response. The failure mode the docs describe is the useful and unusual detail: on an under-tier plan the OAuth connection succeeds and only the tool calls fail, with the message "Plan does not include API access", so a buyer can appear connected and still get nothing back. The vendor publishes a copyable agent guide (tool catalogue, credit model, webhooks, export column glossary) as one markdown page, which is the llms.txt idea applied to a tool catalogue and is worth naming as a pattern. STANDING CATEGORY RISK applies in full: LinkedIn's User Agreement prohibits automation and every Sales Navigator scraping tool in this directory carries account-ban risk. The vendor's own site banner on this date advertised a waiting list for a "cookie less Sales Navigator scraper", which is a direct acknowledgement that the current method depends on a logged-in session. 2026-09-07: https://mcp.vayne.io/mcp returned 401 to an MCP initialize POST (https://mcp.vayne.io/mcp).

## Named capabilities
Tool names below are reported by sources. Their presence is not a successful call.

## CLI evidence
Status: official
- Reported install command: npm install -g @vayne/cli; source: https://www.npmjs.com/package/@vayne/cli

Read current vendor documentation before configuring or running commands.