Connect Apex by LeadShark — discovery and your agent gets 3 tools, among them about_apex, first_plays, get_setup_steps. It answers at https://www.apex.new/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 23 October 2026, succeeded.
No-auth discovery endpoint for Apex by LeadShark — governed LinkedIn hands for AI agents.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
about_apex | Read-only: returns what Apex by LeadShark is, tier pricing, and the URL of the real authenticated MCP server. Call this first — this endpoint is a discovery stub with no LinkedIn powers. |
first_plays | Read-only: returns copy-paste starter prompts for the first session after connecting the real Apex server — verify, discover, enrich, act. |
get_setup_steps | The 5-step flow to connect an AI agent to the real Apex MCP server: LeadShark account → LinkedIn → 24h Apex unlock → mount MCP → first Loadout. |
Every block below points at https://www.apex.new/mcp. Pick your client and copy.
claude mcp add --transport http apex-by-leadshark-discovery https://www.apex.new/mcp
{
"mcpServers": {
"apex-by-leadshark-discovery": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://www.apex.new/mcp"]
}
}
}{
"mcpServers": {
"apex-by-leadshark-discovery": {
"url": "https://www.apex.new/mcp"
}
}
}{
"servers": {
"apex-by-leadshark-discovery": {
"type": "http",
"url": "https://www.apex.new/mcp"
}
}
}{
"context_servers": {
"apex-by-leadshark-discovery": {
"url": "https://www.apex.new/mcp"
}
}
}{
"mcpServers": {
"apex-by-leadshark-discovery": {
"serverUrl": "https://www.apex.new/mcp"
}
}
}{
"mcpServers": {
"apex-by-leadshark-discovery": {
"url": "https://www.apex.new/mcp"
}
}
}name: Apex by LeadShark — discovery
version: 0.0.1
schema: v1
mcpServers:
- name: Apex by LeadShark — discovery
type: streamable-http
url: https://www.apex.new/mcp{
"mcpServers": {
"apex-by-leadshark-discovery": {
"httpUrl": "https://www.apex.new/mcp"
}
}
}{
"mcpServers": {
"apex-by-leadshark-discovery": {
"type": "http",
"url": "https://www.apex.new/mcp"
}
}
}{
"mcpServers": {
"apex-by-leadshark-discovery": {
"url": "https://www.apex.new/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fwww.apex.new%2Fmcp&type=streamable_http&id=apex-by-leadshark-discovery&name=Apex%20by%20LeadShark%20%E2%80%94%20discovery
It answered our last check on 23 October 2026 in 228 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
3, as returned by the server's own tools/list on 20 September 2026: about_apex, first_plays, get_setup_steps.
It answered our last check on 23 October 2026 in 228 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://www.apex.new/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.rzere. Endpoint host: www.apex.new. ARD identifier: urn:air:io.github.rzere:mcp:linkedin-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.