MCP servers observed by Lowdown
io.github.Linked-API/linkedapi-mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 94 tools listed. On 2026-11-17 a tool description with a URL appeared (new domain: www.linkedin.com). MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Linked-API/linkedapi-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Linked-API/linkedapi-mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-17: input or output schemas changed, descriptions changed, tool names changed; tool count 84 → 94; a tool description with a URL appeared (www.linkedin.com)
- 2026-11-14: input or output schemas changed, descriptions changed
What tools does it list?
94 tools on 2026-11-17:
accept_invitationadmin_cancel_connection_sessionadmin_connect_accountadmin_create_reconnection_sessionadmin_delete_limitsadmin_disconnect_accountadmin_get_accountsadmin_get_connection_sessionadmin_get_limitsadmin_get_limits_defaultsadmin_get_limits_usageadmin_get_seatsadmin_get_subscription_statusadmin_regenerate_tokenadmin_reparse_account_infoadmin_reset_limitsadmin_set_limitsadmin_set_seatscheck_connection_statuscomment_on_postcreate_postcreate_repostendorse_person_skillendorse_person_skillsexecute_custom_workflowfetch_companyfetch_jobfetch_personfetch_postget_api_usageget_changelogget_conversationget_inboxget_networkget_workflow_resultignore_invitationmanage_conversationnv_create_listnv_create_saved_searchnv_delete_listnv_delete_saved_searchnv_fetch_companynv_fetch_personnv_get_conversationnv_manage_conversationnv_remove_account_from_listnv_remove_lead_from_listnv_rename_listnv_retrieve_alertsnv_retrieve_list_accountsnv_retrieve_list_leadsnv_retrieve_listsnv_retrieve_saved_searchesnv_save_accountnv_save_leadnv_search_companiesnv_search_peoplenv_send_messagenv_sync_conversationnv_sync_inboxnv_unsave_accountnv_unsave_leadrc_archive_projectrc_create_projectrc_fetch_personrc_rename_projectrc_retrieve_project_candidatesrc_retrieve_projectsrc_save_to_projectrc_search_peoplerc_send_messagerc_sync_inboxreact_to_commentreact_to_postremove_connectionreply_to_commentretrieve_connectionsretrieve_feedretrieve_invitationsretrieve_pending_requestsretrieve_performanceretrieve_profile_viewersretrieve_ssisearch_companiessearch_jobssearch_peoplesearch_postssend_connection_requestsend_feedbacksend_messagesync_conversationsync_inboxsync_networkwithdraw_connection_request
MCP Registry declaration
- Registry name:
io.github.Linked-API/linkedapi-mcp - Declared version: 2.3.21
- Status: active
- Declared hosts:
mcp.linkedapi.io
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.Linked-API/linkedapi-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Linked-API/linkedapi-mcp?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.Linked-API/linkedapi-mcp -- npx -y @linkedapi/mcp
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).