mcpbeat

Apex by LeadShark — discovery MCP Server

io.github.rzere/linkedin-mcp
not responding

Apex by LeadShark — discovery is listed as active in the registry but did not answer our last check. It exposes 3 tools. Last commit 13 Jul 2026.

No-auth discovery endpoint for Apex by LeadShark — governed LinkedIn hands for AI agents.

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
0.0%
Uptime 24h
0 of 91 checks
3
Tools
read from the server
90 ms
Response time
average over 24h
0
Stars
last commit 13 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add linkedin-mcp --transport http https://www.apex.new/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "linkedin-mcp": {
      "url": "https://www.apex.new/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.linkedin-mcp]
url = "https://www.apex.new/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "linkedin-mcp": {
      "url": "https://www.apex.new/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "linkedin-mcp": {
      "url": "https://www.apex.new/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

about
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
first_plays
Read-only: returns copy-paste starter prompts for the first session after connecting the real Apex server — verify, discover, enrich, act.
setup
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.

Endpoints

URLTransportStateLatencyChecked
https://www.apex.new/mcp streamable-http answering 90 ms 13 min ago

Apex by LeadShark — discovery — questions

Answers built from our own checks of this server.

What can Apex by LeadShark — discovery do?
It exposes 3 tools, read directly from the server on our last check. Among them: about_apex, first_plays, get_setup_steps. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Apex by LeadShark — discovery working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 90 ms. The bar chart above shows every period we have measured.
The registry lists Apex by LeadShark — discovery as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Apex by LeadShark — discovery?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Apex by LeadShark — discovery need an API key?
No. Apex by LeadShark — discovery completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
Is Apex by LeadShark — discovery open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.