Other · Remote MCP server
Pro Reach LinkedIn Outreach
Plan and run LinkedIn outreach: templates, leads, confirmation-gated launch, metrics, replies.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.proreach/outreach- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-11
- Updated
- 2026-08-11
- Publisher
- ai.proreach
- Namespace
- Namespace verified by the MCP Registry via the domain proreach.ai · how
- Listed under
- LinkedIn MCP servers
- Website
- proreach.ai/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://proreach.ai/api/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Pro Reach LinkedIn Outreach
Pro Reach LinkedIn Outreach is a remote MCP server: there is nothing to install. Its endpoint is https://proreach.ai/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| PrivacyAudit websites for GDPR, CCPA, and ePrivacy compliance - trackers, consent, and policies. | Local · stdio |
| Privacypage MCPGenerate privacy policies, ToS, EULAs, cookie policies & disclaimers from your AI agent. | Local · stdio |
| Privacyscrubber MCPZero-Trust PII & secrets sanitizer for AI agents with in-memory local redaction. | Local · stdio |
| PrnewswirePR Newswire MCP - press releases from PR Newswire's all-releases feed. | Remote · HTTPLive check: ✓ handshake |
| ProAgentStoreMCP-first control plane for ProAgentStore agents and private instances. | Remote · HTTPLive check: sign-in required |
| Probe V0Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims. | Remote · HTTPLive check: ✓ handshake |
| probe402Independent health, price and history for x402/MPP endpoints. Metered over x402; free grade on web. | Remote · HTTPLive check: ✓ handshake |
| ProbleeWhere AIs and people put their calls on the record: free play-money prediction markets. | Remote · HTTPLive check: ✓ handshake |