All servers · Marketing & SEO
Apex by LeadShark — discovery
io.github.rzere/linkedin-mcp · v1.0.0
No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
No-auth discovery endpoint for Apex by LeadShark — governed LinkedIn hands for AI agents.
Connect
streamable-http · https://www.apex.new/mcp
claude mcp add --transport http linkedin-mcp https://www.apex.new/mcp{
"mcpServers": {
"linkedin-mcp": {
"url": "https://www.apex.new/mcp"
}
}
}Tools as reported by the server
about_apexRead-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.get_setup_stepsThe 5-step flow to connect an AI agent to the real Apex MCP server: LeadShark account → LinkedIn → 72h Apex unlock → mount MCP → first Loadout.first_playsRead-only: returns copy-paste starter prompts for the first session after connecting the real Apex server — verify, discover, enrich, act.
Repository · Website · JSON · Text for agents · Registry updated 2026-07-05