Developer Tools

apex.new

Provides information and setup guidance for connecting AI agents to the Apex LeadShark MCP server for lead enrichment.

1 endpoint3 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://www.apex.new/mcp

No auth detected

MCP server metadata

Name: apex-new-discovery
Version: 1.0.0

Capabilities

tools

Server instructions

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. The authenticated operator server (apex.leadshark.io/mcp) needs Apex ($119/mo) or an active 24-hour Apex trial (unlockable once from free trial, Pro, or Pro+). Pro+ MCP is the automation layer only — scheduling, automations, owned inbound — not the full see→decide→act loadout. Call about_apex, get_setup_steps, or first_plays for details you can relay to the user.

Known tools 3

about_apex

Read-only: returns what Apex by LeadShark is, tier pricing, and the URL of the real authenticated MCP server.

Inferred read-only

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.

Inferred read-only

first_plays

Read-only: returns copy-paste starter prompts for the first session after connecting the real Apex server — verify, discover, enrich, act.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.apex-new-discovery]
url = "https://www.apex.new/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "apex-new-discovery": {
      "type": "http",
      "url": "https://www.apex.new/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: apex-new-discovery
Remote MCP URL: https://www.apex.new/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "apex-new-discovery": {
      "url": "https://www.apex.new/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "apex-new-discovery": {
      "type": "http",
      "url": "https://www.apex.new/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "apex-new-discovery",
  "transport": "streamable-http",
  "url": "https://www.apex.new/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for apex.new was fetched 2026-07-26T08:30:22.222Z and is being refreshed.

Trust status Neutral

apex.new is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.