Fresh Linkedin Profile Data MCP Server
Related Servers
Alternatives to Fresh Linkedin Profile Data MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables access to LinkedIn data through the Li Data Scraper API, supporting profile enrichment, company details, people search, post interactions, and activity tracking.20MIT
- AlicenseCqualityDmaintenanceEnables access to LinkedIn data including profile enrichment, company information, job searches, post analytics, and social interactions through the LinkedIn Api8 API with comprehensive search and data retrieval capabilities.51MIT
- AlicenseCqualityDmaintenanceEnables access to comprehensive LinkedIn data, including professional profile details, company information, and social engagement metrics. It supports searching for people, retrieving posts and comments, and fetching detailed experience, skills, and recommendations.52MIT
- AlicenseAqualityBmaintenanceEnables capturing recent posts from LinkedIn profiles and company pages, including real reaction and comment counts and publicly visible commenters, without requiring a LinkedIn account, cookies, or credentials.148MIT
- AlicenseNot gradedqualityCmaintenanceEnables reading LinkedIn profiles into structured JSON using your own signed-in session, with no browser automation or API keys.MIT
- FlicenseNot gradedqualityDmaintenanceEnables extraction of comprehensive LinkedIn profile data including experience, education, skills, and contact information through browser automation. Requires manual LinkedIn credentials input and uses anti-detection measures for reliable scraping.5-
TDQS
Scored across 39 tools
There are multiple overlapping company and lead search tools (search_companies, get_companies, search_companies_instantly, search_companies_by_sn_url, search_leads, search_leads_v2, lead_search_at_scale), some with identical 'Get search results' descriptions. While many retrieval tools are distinct, the boundary between async search, status, and result-fetching endpoints is easy for an agent to confuse.
The set mixes get_* and search_* patterns with exceptions like count, enrich_lead, find_custom_headcount, google_profiles, and lead_search_at_scale. It also contains inconsistent v2 suffixes, generic names, and the typo get_companys_posts, making the naming pattern unreliable.
39 tools is far beyond the typical well-scoped MCP surface, even for a broad LinkedIn data product. The count feels bloated largely because search functionality is split across many overlapping variants rather than consolidated.
For a read-only LinkedIn data enrichment server, the surface covers companies, profiles, posts, jobs, leads, decision makers, and school/company searches quite thoroughly. Minor gaps exist, such as no explicit employee-list or full profile-experience endpoint, but most lead-generation workflows have no dead ends.