# com.mambabuilt/mcp-person-linkedin-url-resolver (npm · @mambalabsdev/mcp-person-linkedin-url-resolver)

Find a person's LinkedIn profile URL from name and company, with a match confidence.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- npm · `@mambalabsdev/mcp-person-linkedin-url-resolver`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-mambabuilt-mcp-person-linkedin-url-resolver/mambalabsdev-mcp-person-linkedin-url-resolver.md), [page](https://verifymcp.io/servers/com-mambabuilt-mcp-person-linkedin-url-resolver/mambalabsdev-mcp-person-linkedin-url-resolver)

## Channel facts

- Registry: `npm`
- Package: `@mambalabsdev/mcp-person-linkedin-url-resolver`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 406 tokens (~406/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.mambabuilt/mcp-person-linkedin-url-resolver server?

com.mambabuilt/mcp-person-linkedin-url-resolver runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-person-linkedin-url-resolver. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-mambabuilt-mcp-person-linkedin-url-resolver -- npx -y @mambalabsdev/mcp-person-linkedin-url-resolver
```

### Cursor

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-person-linkedin-url-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-person-linkedin-url-resolver"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mambabuilt-mcp-person-linkedin-url-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-person-linkedin-url-resolver"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-mambabuilt-mcp-person-linkedin-url-resolver -- npx -y @mambalabsdev/mcp-person-linkedin-url-resolver
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mambabuilt-mcp-person-linkedin-url-resolver": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mambalabsdev/mcp-person-linkedin-url-resolver"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mambabuilt-mcp-person-linkedin-url-resolver --command npx --arg -y --arg @mambalabsdev/mcp-person-linkedin-url-resolver
```

### Hermes

```yaml
mcp_servers:
  com-mambabuilt-mcp-person-linkedin-url-resolver:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-person-linkedin-url-resolver"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-mambabuilt-mcp-person-linkedin-url-resolver": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mambalabsdev/mcp-person-linkedin-url-resolver"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mambabuilt-mcp-person-linkedin-url-resolver -t stdio -c npx -a -y @mambalabsdev/mcp-person-linkedin-url-resolver
```

### Other

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-person-linkedin-url-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-person-linkedin-url-resolver"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 68)

First indexed and scored.

## MCP tools (1)

### `resolve_person_linkedin_url` (~406 tokens)

Resolve a person's LinkedIn URL

Find a person's LinkedIn profile URL from their name and company domain or company name, read from Google result pages through the Apify Google SERP proxy; LinkedIn itself is never opened. Returns one row per person with linkedin_url, match_status (found at a confidence of 0.8 or more with a clear lead over any other profile, ambiguous with the likely URL, not_found, or blocked), match_confidence from 0 to 1, name_match, company_match (current, former, mentioned, none), the headline, snippet, and follower count Google shows, and the runner up. Batch up to 500 persons in persons. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges one event per person searched (found, ambiguous, or not found); blocked and error rows are free.

Input parameters:

- `allow_name_only` (string): true searches a person with no company; such a row is never found, only ambiguous. Default false.
- `company_domain` (string): The company domain, for example hashicorp.com. Give this or company_name.
- `company_name` (string): Optional. The company name as people write it, used instead of the word in the domain.
- `country` (string): Two letter Google country code. Default us.
- `full_name` (string): The person's first and last name, for example Armon Dadgar.
- `job_title` (string): Optional. A headline that agrees gets a small boost.
- `keywords` (string): Optional extra words for the Google query.
- `location` (string): Optional city or country. A small boost when the snippet agrees.
- `max_charge_usd` (string): Optional. The run stops before a charge that would pass this amount.
- `persons` (array): Several persons, one per line as Full Name | company.com | job title. Up to 500.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-mambabuilt-mcp-person-linkedin-url-resolver/mambalabsdev-mcp-person-linkedin-url-resolver#diagnostics

## Score history

- 2026-10-25: 70
- 2026-10-24: 69
- 2026-10-23: 69
- 2026-10-22: 68

## Common questions

### What is the com.mambabuilt/mcp-person-linkedin-url-resolver server?

com.mambabuilt/mcp-person-linkedin-url-resolver is listed in the public MCP registry as com.mambabuilt/mcp-person-linkedin-url-resolver. Find a person's LinkedIn profile URL from name and company, with a match confidence. This page covers its npm package (@mambalabsdev/mcp-person-linkedin-url-resolver).

### Is the com.mambabuilt/mcp-person-linkedin-url-resolver server safe to use?

com.mambabuilt/mcp-person-linkedin-url-resolver scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the com.mambabuilt/mcp-person-linkedin-url-resolver server expose?

com.mambabuilt/mcp-person-linkedin-url-resolver exposes 1 tool: resolve_person_linkedin_url. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.

### Is the com.mambabuilt/mcp-person-linkedin-url-resolver server still maintained?

com.mambabuilt/mcp-person-linkedin-url-resolver is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the com.mambabuilt/mcp-person-linkedin-url-resolver server under?

com.mambabuilt/mcp-person-linkedin-url-resolver declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@mambalabsdev/mcp-person-linkedin-url-resolver
- Socket report: https://socket.dev/npm/package/@mambalabsdev/mcp-person-linkedin-url-resolver
- Repository: https://github.com/mambalabsdev/mcp-person-linkedin-url-resolver
- Changelog RSS feed: https://verifymcp.io/servers/com-mambabuilt-mcp-person-linkedin-url-resolver/mambalabsdev-mcp-person-linkedin-url-resolver.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mambabuilt-mcp-person-linkedin-url-resolver/mambalabsdev-mcp-person-linkedin-url-resolver.json
- HTML version of this page: https://verifymcp.io/servers/com-mambabuilt-mcp-person-linkedin-url-resolver/mambalabsdev-mcp-person-linkedin-url-resolver