Apex by LeadShark — discovery

Name: Apex by LeadShark — discovery
Author: rzere

MCP serverMCP

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

by rzererepository ↗homepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"apex-by-leadshark-discovery","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability109/109 checks ok

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	184 ms	server apex-new-discovery 1.0.0 · protocol 2025-06-18 · 3 tools
11 h ago	mcp initialize	ok	200	133 ms	server apex-new-discovery 1.0.0 · protocol 2025-06-18 · 3 tools
18 h ago	mcp initialize	ok	200	182 ms	server apex-new-discovery 1.0.0 · protocol 2025-06-18 · 3 tools
25 h ago	mcp initialize	ok	200	173 ms	server apex-new-discovery 1.0.0 · protocol 2025-06-18 · 3 tools
32 h ago	mcp initialize	ok	200	143 ms	server apex-new-discovery 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	143 ms	server apex-new-discovery 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	158 ms	server apex-new-discovery 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	135 ms	server apex-new-discovery 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	138 ms	server apex-new-discovery 1.0.0 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	135 ms	server apex-new-discovery 1.0.0 · protocol 2025-06-18 · 3 tools

Tools observed via MCP handshake

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

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.rzere/linkedin-mcp

first seen 1 mo ago · fetched 2 d agoopen ↗

Field history (7 recent events)

1 mo ago · declared · summary → "No-auth discovery endpoint for Apex by LeadShark — governed LinkedIn hands for AI agents."
1 mo ago · declared · description → "No-auth discovery endpoint for Apex by LeadShark — governed LinkedIn hands for AI agents."
1 mo ago · declared · publisherName → "rzere"
1 mo ago · declared · homepageUrl → "https://www.apex.new"
1 mo ago · declared · repoUrl → "https://github.com/rzere/linkedin-mcp"
1 mo ago · declared · version → "1.0.0"
1 mo ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from