Skip to main content
Glama
mambalabsdev

Person LinkedIn URL Resolver MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Person LinkedIn URL Resolver MCP Server

No user-submitted related servers found.

    Related Servers

    • LinkedIn MCP Server

      Dev-Anandhan
      A
      license
      A
      quality
      D
      maintenance
      Enables searching and scraping of LinkedIn profiles, companies, jobs, and posts using natural language through MCP-compatible AI clients.
      13
      MIT

    • linkedin-mcp

      AryanRajMaurya
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-capable agents to read and update a LinkedIn profile, check and publish posts through the official LinkedIn API. Includes a built-in quality gate that blocks drafts reading as machine-generated before anything reaches the public feed.
      5
      MIT

    • LinkedInMCP

      SandeshKhilari01
      A
      license
      Not graded
      quality
      D
      maintenance
      An innovative MCP server that transforms LinkedIn API interactions, enabling advanced people search, profile retrieval, and job market intelligence through natural language.
      49 npm
      MIT

    • LinkedIn MCP Server

      aarnav-hariramani
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible clients to read LinkedIn profiles, companies, and jobs, and to send connection requests after explicit confirmation, using interactive browser-based authentication instead of stored credentials.
      8
      MIT

    • LinkedIn MCP

      devag7
      A
      license
      A
      quality
      A
      maintenance
      Released 3.0.0: 22 MCP tools, guided offline setup, local stdio, Chrome and manual login. No hosted deployment or job-research brief. Writes need opt-in, reviewed preview and human approval. Unofficial; provider compatibility, first-use cohorts, coordinated erasure and Windows privacy proof remain unverified. No mandatory paid service.
      22
      192 npm
      12
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of misselection or overlap with a sibling. Its purpose is stated precisely (name + company → LinkedIn URL via Google SERP), leaving no ambiguity about what it does or does not do.

    Naming Consistency5/5

    The single name resolve_person_linkedin_url follows a clear verb_object convention in snake_case. Nothing else exists to break the pattern, and the name is fully self-describing.

    Tool Count3/5

    The server's scope is deliberately narrow (one resolution operation), so a single tool is defensible and it absorbs volume via the 500-person batch parameter. Still, a one-tool surface is thin, and the run-ID error path hints at lifecycle operations that were folded into the blob rather than exposed as tools.

    Completeness4/5

    The single tool covers the core workflow end to end: batch input, structured output with confidence, match status, matched components, and runner-up, plus explicit blocked/error semantics. The notable gap is that failures return a run ID with no companion tool to retrieve or retry that run, which an agent cannot work around from this surface alone.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources