Apex by LeadShark — discovery
No-auth discovery endpoint for Apex by LeadShark — governed LinkedIn hands for AI agents.
我該用這個嗎
品質與安全性
B
根據工具定義與協定合規性的自動化分析。
上下文成本
~198Token(工具定義)
~186 B典型回應大小
極小的注意力影響(128k 上下文的 0.15%)
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案:
{
"mcpServers": {
"linkedin-mcp": {
"url": "https://www.apex.new/mcp"
}
}
}遠端端點
https://www.apex.new/mcpstreamable-http它能做什麼
工具清單
工具(3)
🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢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.
輸入結構描述
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟢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.
輸入結構描述
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟢first_plays
Read-only: returns copy-paste starter prompts for the first session after connecting the real Apex server — verify, discover, enrich, act.
輸入結構描述
{
"type": "object",
"properties": {},
"additionalProperties": false
}社群
證據
近期觀測
已驗證未記錄版本3 個工具
已驗證未記錄版本3 個工具