Other · Remote MCP server
LinkedNav
Run LinkedIn outreach from your AI chat: find leads, launch campaigns, send, and reply.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.linglistack/linkednav-mcp- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-19
- Updated
- 2026-08-19
- Publisher
- linglistack (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/linglistack) · how
- Listed under
- LinkedIn MCP servers
- Website
- www.linkednav.com
- Repository
- github.com/linglistack/linkednav-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.linkednav.com/ | 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; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect LinkedNav
LinkedNav is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.linkednav.com/, 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 |
|---|---|
| LinkedInRead LinkedIn profiles, companies, jobs and messages via your own browser session. | Local · stdio |
| Linkedin Buying SignalsFind B2B prospects showing buying signals on LinkedIn and draft the outreach. | Remote · HTTPLive check: ✓ handshake |
| LinkedIn Content PlannerDraft, revise and review LinkedIn posts; a human approves each one before it goes live. | Remote · HTTPLive check: sign-in required |
| LinkedIn Decision Maker FinderFind decision makers at any company: name, job title and LinkedIn profile URL. No login needed. | Remote · HTTPLive check: sign-in required |
| LinkheftDomain authority API + MCP: 0-100 score, rank, trend, 50/call. $19/mo; 1,000 free lookups/day. | Remote · HTTPLive check: ✓ handshake |
| LinkIntelEvidence for your AI's next X post: your post metrics, X ranking weights and chosen references. | Remote · HTTPLive check: sign-in required |
| LinkLoreAI-native structured memory for agents (MCP). Built for agents, not humans. | Local · stdio |
| LinklyCreate and manage short links, track clicks, and automate URL management. | Remote · HTTPLive check: ✓ handshake |