Person Linkedin URL Resolver MCP server
Find a person's LinkedIn profile URL from name and company, with a match confidence.
0 stars163 downloads/wk
Reviews
Write oneNobody has reviewed Person Linkedin URL Resolver yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Person Linkedin URL Resolver tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
resolve_person_linkedin_url
Public scan report
scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 3 days ago15/15
- Maintainer identitynamespace and repository owner differ4/10
How Person Linkedin URL Resolver compares
Against every graded Sales and outbound MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 876 Sales and outbound servers
- Tools
- 1
- the typical Sales and outbound server has 8
- Tools that change things
- 0%
- typical: 11%. Fewer write tools means less an agent can break
- Downloads a week
- 163
- more than 72% of 156 Sales and outbound servers with a package
What its tools let an agent do: 1 read
Install Person Linkedin URL Resolver in Claude Code, Cursor or VS Code
Runs npx -y @mambalabsdev/mcp-person-linkedin-url-resolver on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-person-linkedin-url-resolver -- npx -y @mambalabsdev/mcp-person-linkedin-url-resolver
What the publisher says
From the Person Linkedin URL Resolver repository's README, as published. We do not edit it. Read it on GitHub
Person LinkedIn URL Resolver MCP Server
Give it a person's name and company domain (or company name). Each run reads Google result pages through the Apify Google SERP proxy and returns one row per person with the LinkedIn profile URL, the headline and follower count Google shows, and a match confidence. It never opens LinkedIn and needs no LinkedIn account.
What's Inside
- What it does
- Quick start
- Prerequisites
- Example prompts
- Tool
- Inputs
- Pricing
- Your keys
- Full actor documentation
- License
What it does
- matchstatus is found at a confidence of 0.8 or more with a clear lead over every other profile, ambiguous (the likely URL), notfound, or blocked.
- company_match says whether the company is current (headline or a present role), former (marked prev, ex, or former), or only mentioned.
- Posts, articles, and directory pages are dropped; only /in/ profile URLs are returned.
All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config (claudedesktopconfig.json), Cursor, or any MCP client:
{
"mcpServers": {
"mamba-person-linkedin-url-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-person-linkedin-url-resolver"
],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}Restart the client. The resolvepersonlinkedin_url tool appears.
Prerequisites
- Node.js 18 or newer.
- An Apify API token from console.apify.com/account/integrations, set as APIFY_TOKEN. The server lists its tool without a token; a call needs one.
Example prompts
- "Find the LinkedIn profile of Armon Dadgar at hashicorp.com."
- "Here are 20 names and company domains from my CRM. Find each LinkedIn URL and tell me which ones are certain."
Tool
resolvepersonlinkedin_url. One tool. Example arguments:
{ "full_name": "Armon Dadgar", "company_domain": "hashicorp.com" }Inputs
Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Person Linkedin URL Resolver: common questions
- Is Person Linkedin URL Resolver MCP server safe?
- Mostly: it is graded B (77/100). Read the Person Linkedin URL Resolver safety report
- How do I install Person Linkedin URL Resolver?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Person Linkedin URL Resolver need an API key?
- Yes. The registry entry asks for
APIFY_TOKEN. - Is Person Linkedin URL Resolver maintained?
- The last commit was 13 days ago (2026-10-22). The latest release is v1.0.0.
- What can I use instead of Person Linkedin URL Resolver?
- Servers from other publishers that do the same job: LinkedIn Toolkit MCP server, Generect MCP server and YourICP MCP server. Compare all Person Linkedin URL Resolver alternatives.
- How does Person Linkedin URL Resolver compare with other Sales and outbound MCP servers?
- safety score 77/100 (higher than 50% of 876 Sales and outbound servers); tools 1 (the typical Sales and outbound server has 8); tools that change things 0% (typical: 11%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Person Linkedin URL Resolver
Same job from other publishers: the closest match first, then the best rated.
- LinkedIn ToolkitLinkedIn for AI agents from your own Chrome session: search, profiles, lists, outreach queue.not reviewedGrowingA
GenerectB2B lead and company data for AI agents: free search, pay only for emails, phones, profiles.not reviewedGrowingA
YourICPEnrich contacts by email or LinkedIn URL and build targeted B2B audiences.not reviewedGrowingA
Linkedin Datasuperagnt: marketing plugin for Claude and ChatGPT. Know your market: LinkedIn profiles and posts.not reviewedGrowingA- LinkedIn MCP ServerLinkedIn API as MCP tools to retrieve profile data and publish content. Powered by HAPI MCP.not reviewedGrowingB