# io.github.johnisanerd/linkedin-jobs (remote · mcp.apify.com)

LinkedIn jobs by keyword and location, with salary, description, and apply links, via hosted MCP.

- Trust score: 48/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.apify.com`: 48/100 (this document), [markdown](https://verifymcp.io/servers/johnisanerd-linkedin-jobs/mcp.md), [page](https://verifymcp.io/servers/johnisanerd-linkedin-jobs/mcp)

## Channel facts

- Endpoint: `https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 86/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the io.github.johnisanerd/linkedin-jobs MCP server?

io.github.johnisanerd/linkedin-jobs is a hosted endpoint at https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api, so there is nothing to install locally. 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 --transport http johnisanerd-linkedin-jobs 'https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api'
```

### Cursor

```json
{
  "mcpServers": {
    "johnisanerd-linkedin-jobs": {
      "url": "https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "johnisanerd-linkedin-jobs": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api"
    }
  }
}
```

### Codex

```toml
[mcp_servers.johnisanerd-linkedin-jobs]
url = "https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "johnisanerd-linkedin-jobs": {
      "type": "remote",
      "url": "https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add johnisanerd-linkedin-jobs --url 'https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  johnisanerd-linkedin-jobs:
    url: "https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api"
```

### Netclaw

```json
{
  "McpServers": {
    "johnisanerd-linkedin-jobs": {
      "Transport": "http",
      "Url": "https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api"
    }
  }
}
```

### Vellum

```bash
assistant mcp add johnisanerd-linkedin-jobs -t streamable-http -u 'https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api'
```

### Other

```json
{
  "mcpServers": {
    "johnisanerd-linkedin-jobs": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 48)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/johnisanerd-linkedin-jobs/mcp#diagnostics

## Score history

- 2026-11-05: 48

## Common questions

### What is the io.github.johnisanerd/linkedin-jobs MCP server?

io.github.johnisanerd/linkedin-jobs is an MCP server listed in the public MCP registry as io.github.johnisanerd/linkedin-jobs. LinkedIn jobs by keyword and location, with salary, description, and apply links, via hosted MCP. This page covers its hosted endpoint (https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api).

### Is the io.github.johnisanerd/linkedin-jobs MCP server safe to use?

io.github.johnisanerd/linkedin-jobs scores 48 out of 100 on VerifyMCP. 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.

### Does the io.github.johnisanerd/linkedin-jobs MCP server require authentication?

Yes. io.github.johnisanerd/linkedin-jobs asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.johnisanerd/linkedin-jobs MCP server still maintained?

io.github.johnisanerd/linkedin-jobs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the io.github.johnisanerd/linkedin-jobs MCP server?

VerifyMCP ran 7 checks on io.github.johnisanerd/linkedin-jobs, covering TLS certificate, Authorization, HTTPS, HSTS header and 3 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.johnisanerd/linkedin-jobs: Schema quality, Stability, Tool coverage and Tool safety. 4 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.apify.com/?tools=johnvc/linkedin-jobs-api
- Repository: https://github.com/johnisanerd/Apify-LinkedIn-Jobs-API
- Website: https://apify.com/johnvc/linkedin-jobs-api?fpr=9n7kx3&fp_sid=mcpregistry
- Changelog RSS feed: https://verifymcp.io/servers/johnisanerd-linkedin-jobs/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/johnisanerd-linkedin-jobs/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/johnisanerd-linkedin-jobs/mcp.json
- HTML version of this page: https://verifymcp.io/servers/johnisanerd-linkedin-jobs/mcp