Skip to content

Apex by LeadShark — discovery

by rzere · remote · no sign-in to list tools · v1.0.0 · published by GitHub user rzere

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

Read only
CompareRegistry entry

3 tools: 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http linkedin https://www.apex.new/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Only reads 3Claude Code: allow
  • about_apexRead-only: returns what Apex by LeadShark is, tier pricing, and the URL of the real authenticated MCP server.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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_playsRead-only: returns copy-paste starter prompts for the first session after connecting the real Apex server — verify, discover, enrich, act.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read-only: returns copy-paste starter prompts for the first session after connecting the real Apex server — verify, discover, enrich, act.
  • 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.No findings

    Why it is in this group

    • The name "get_setup_steps" says "get": a word for reading.
    Description, as the server wrote it
    The 5-step flow to connect an AI agent to the real Apex MCP server: LeadShark account → LinkedIn → 72h Apex unlock → mount MCP → first Loadout.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http linkedin https://www.apex.new/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__linkedin__about_apex",
      "mcp__linkedin__get_setup_steps",
      "mcp__linkedin__first_plays"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as linkedin. Review it before you use it.