Apex by LeadShark — discovery
by apex.new in Company & people data
No-auth discovery endpoint for Apex by LeadShark — governed LinkedIn hands for AI agents.
https://www.apex.new/mcp- Tools
- 3
- open to any client
- Uptime
- 100%
- last 30 days
- Response time
- 365 ms
- 460 ms slowest 5%
- Last check
- Passed
- 8 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"apex-by-leadshark-discovery": {
"type": "http",
"url": "https://www.apex.new/mcp"
}
}
}3 tools
- 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 stub with no LinkedIn powers.
- 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.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 8 h ago | Passed | 200 | 394 ms |
| 18 h ago | Passed | 200 | 393 ms |
| 28 h ago | Passed | 200 | 351 ms |
| 37 h ago | Passed | 200 | 385 ms |
| 46 h ago | Passed | 200 | 337 ms |
Show 10 older checks
| 2 days ago | Passed | 200 | 357 ms |
| 3 days ago | Passed | 200 | 465 ms |
| 3 days ago | Passed | 200 | 368 ms |
| 4 days ago | Passed | 200 | 335 ms |
| 4 days ago | Passed | 200 | 280 ms |
| 5 days ago | Passed | 200 | 460 ms |
| 5 days ago | Passed | 200 | 348 ms |
| 5 days ago | Passed | 200 | 365 ms |
| 6 days ago | Passed | 200 | 321 ms |
| 6 days ago | Passed | 200 | 336 ms |