Skip to content
External endpointresponds

Apex by LeadShark — discovery

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

Endpoint URL
https://www.apex.new/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
296 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.rzere/linkedin-mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
apex-new-discovery
Version
1.0.0
Capability keys
tools
Tool names
about_apex, get_setup_steps, first_plays
Instructions excerpt

This is the discovery endpoint for Apex by LeadShark (apex.new). It has no LinkedIn powers of its own — it exists to complete the handshake and tell you where the real operator server is. The full Apex MCP loadout (40 tools: discover, enrich, comment, connect, message, email — all governed) is a separate authenticated server at https://apex.leadshark.io/mcp. Connect it as a custom connector / MCP server and sign in with a LeadShark account. Call about_apex, get_setup_steps, or first_plays for details you can relay to the user.

Reported Aug 17, 2026, 05:08 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 229ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 388ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 221ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 296ms
Back to MCP directory