Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.jojapi/linkedin

REMOTE · MCP.JOJAPI.COM · SCANNED OCT 4

LinkedIn: The LinkedIn Data API offers access to detailed information on individuals, companies.

Available components

+14 this week 76 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1485 tokens (~123/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the com.jojapi/linkedin MCP server?

com.jojapi/linkedin is a hosted endpoint at https://mcp.jojapi.com/linkedin, 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.

remote · mcp.jojapi.com

# add to Claude Code
claude mcp add --transport http com-jojapi-linkedin 'https://mcp.jojapi.com/linkedin'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-jojapi-linkedin": {
      "url": "https://mcp.jojapi.com/linkedin"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-jojapi-linkedin": {
      "type": "http",
      "url": "https://mcp.jojapi.com/linkedin"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-jojapi-linkedin]
url = "https://mcp.jojapi.com/linkedin"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-jojapi-linkedin": {
      "type": "remote",
      "url": "https://mcp.jojapi.com/linkedin",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-jojapi-linkedin --url 'https://mcp.jojapi.com/linkedin' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-jojapi-linkedin:
    url: "https://mcp.jojapi.com/linkedin"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-jojapi-linkedin": {
      "Transport": "http",
      "Url": "https://mcp.jojapi.com/linkedin"
    }
  }
}
# add to Vellum
assistant mcp add com-jojapi-linkedin -t streamable-http -u 'https://mcp.jojapi.com/linkedin'
// mcp.json
{
  "mcpServers": {
    "com-jojapi-linkedin": {
      "type": "http",
      "url": "https://mcp.jojapi.com/linkedin"
    }
  }
}

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Oct 26 +14
    • Stability: fail → 0.97 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Sept 26 62
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “get_v1_company_details” was removed ▼ security
    • Tool “get_v1_person_details” was removed ▼ security
    • Tool “get_v1_post_details” was removed ▼ security
    • Tool “get_v1_pulse_details” was removed ▼ security
    • Tool “get_v1_search_peoples” was removed ▼ security
    • Tool “get_v2_autocomplete” was removed ▼ security
    • Tool “get_v2_profile_contact_info” was removed ▼ security
    • Tool “get_v2_profile_details” was removed ▼ security
    • Tool “get_v2_profile_header_details” was removed ▼ security
    • Tool “get_v2_search_all” was removed ▼ security
    • Tool “get_v2_search_people” was removed ▼ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • MCP protocol: unverified → fail ▼ functional
    • Schema quality: pass → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: 8% → 100% ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: fair → good functional
    • New tool “get_company” functional
    • New tool “get_company_companyId_employees” functional
    • New tool “get_company_companyId_jobs” functional
    • New tool “get_company_posts” functional
    • New tool “get_company_search” functional
    • New tool “get_jobs_detail_jobId” functional
    • New tool “get_jobs_search” functional
    • New tool “get_people_search” functional
    • New tool “get_person_profile” functional
    • New tool “get_person_profile_posts” functional
    • New tool “get_posts_postId_comments” functional
    • New tool “get_posts_postId_reactions” functional
  • 4 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.50 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 19 Aug 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Oct 2026 · Probed https://mcp.jojapi.com/linkedin

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.jojapi.com CN=WE1,O=Google Trust Services,C=US 19 Aug 2026 17 Nov 2026 ECDSA 256 ECDSA-SHA256 6bf56e5f5706ef0d0eece5dccb581199
SANs: mcp.jojapi.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.jojapi.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
jojapi.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.jojapi.com/linkedin Verified 200
http (plaintext) http://mcp.jojapi.com/linkedin HTTPS enforced 301 https://mcp.jojapi.com/linkedin
MCP tools · 12 exposed · ~1,396 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_company ~127

Provide either `slug` or `companyId`. If neither is given, the request fails with `400 VALIDATION_ERROR`. Take the `slug` from a `/company/search` result rather than guessing it from the company name — a company's slug often differs from its display name. Group: Companies. Billing per call: 1 Credits.

NameTypeReqDescription
companyIdstring–The company's numeric identifier. Required unless `slug` is provided.
slugstring–The company's short name, as it appears in its LinkedIn URL. Required unless `companyId` is provided.

No output schema declared.

No examples provided.

get_company_companyId_employees ~144

Returns people who list this company as their employer. Results may include private or out-of-network profiles, which appear with the name `LinkedIn Member`. Full profiles cannot be retrieved for those records, so check the name before calling `/person-profile` with the returned `memberId`. Group: Companies. Billing per call: 1 Credits.

NameTypeReqDescription
companyIdstringyesThe company's numeric identifier, from `/company/search` or `/company`.
countinteger–Number of results per page.
startinteger–Offset of the first result. Pass the `cursor` value from the previous response to fetch the next page.

No output schema declared.

No examples provided.

get_company_companyId_jobs ~115

Returns an empty list if the company has no open postings. Use the `jobId` from a result with `/jobs/detail/{jobId}`. Group: Companies. Billing per call: 1 Credits.

NameTypeReqDescription
companyIdstringyesThe company's numeric identifier, from `/company/search` or `/company`.
countinteger–Number of results per page.
startinteger–Offset of the first result. Pass the `cursor` value from the previous response to fetch the next page.

No output schema declared.

No examples provided.

get_company_posts ~103

Returns the same post structure as `/person-profile/posts`. This endpoint is addressed by `slug` only. Group: Companies. Billing per call: 1 Credits.

NameTypeReqDescription
countinteger–Number of posts per page.
slugstringyesThe company's short name, as it appears in its LinkedIn URL.
startinteger–Offset of the first result. Pass the `cursor` value from the previous response to fetch the next page.

No output schema declared.

No examples provided.

get_company_search ~103

Use the `slug` or `companyId` from a result to fetch full details from `/company`, the employee list, or the job list. Group: Companies. Billing per call: 1 Credits.

NameTypeReqDescription
countinteger–Number of results per page.
keywordstringyesFree-text search term.
startinteger–Offset of the first result. Pass the `cursor` value from the previous response to fetch the next page.

No output schema declared.

No examples provided.

get_jobs_detail_jobId ~87

Returns the full description for a posting. Several fields are only present on some postings; the company name is most reliably taken from the search result that provided the `jobId`. Group: Jobs. Billing per call: 1 Credits.

NameTypeReqDescription
jobIdstringyesThe posting's identifier, from `/jobs/search` or `/company/{companyId}/jobs`.

No output schema declared.

No examples provided.

get_jobs_search ~119

Use the `jobId` from a result with `/jobs/detail/{jobId}`. Group: Jobs. Billing per call: 1 Credits.

NameTypeReqDescription
countinteger–Number of results per page.
geoIdstring–Location code. Türkiye is `102105699`; worldwide is `92000000`.
keywordstringyesSearch term for the job title or description.
startinteger–Offset of the first result. Pass the `cursor` value from the previous response to fetch the next page.

No output schema declared.

No examples provided.

get_people_search ~153

All filters are optional and can be combined. Returns the same person structure as `/company/{companyId}/employees`. Returns an empty list when nothing matches. Group: Person. Billing per call: 1 Credits.

NameTypeReqDescription
companyIdstring–Restrict results to people at this company.
countinteger–Number of results per page.
geoUrnstring–Location code. Türkiye is `102105699`.
keywordstring–Free-text search term.
startinteger–Offset of the first result. Pass the `cursor` value from the previous response to fetch the next page.
titlestring–Restrict results by job title.

No output schema declared.

No examples provided.

get_person_profile ~110

Returns a full profile including experience, education, and skills. Obtain a `memberId` from `/people/search` or `/company/{companyId}/employees`. Note that profiles which are private or outside your network cannot be retrieved; these appear in listings with the name `LinkedIn Member`. Group: Person. Billing per call: 1 Credits.

NameTypeReqDescription
memberIdstringyesA LinkedIn member identifier, returned by `/people/search` and `/company/{companyId}/employees`.

No output schema declared.

No examples provided.

get_person_profile_posts ~104

Returns an empty list if the person has not posted. Group: Person. Billing per call: 1 Credits.

NameTypeReqDescription
countinteger–Number of posts per page.
memberIdstringyesA LinkedIn member identifier, returned by `/people/search` and `/company/{companyId}/employees`.
startinteger–Offset of the first result. Pass the `cursor` value from the previous response to fetch the next page.

No output schema declared.

No examples provided.

get_posts_postId_comments ~115

Returns an empty list when the post has no comments. Group: Posts. Billing per call: 1 Credits.

NameTypeReqDescription
countinteger–Number of results per page.
postIdstringyesThe post's `ugcPostId`, taken from `/person-profile/posts` or `/company/posts`. Use `ugcPostId` here, not `activityId`.
startinteger–Offset of the first result. Pass the `cursor` value from the previous response to fetch the next page.

No output schema declared.

No examples provided.

get_posts_postId_reactions ~116

Returns an empty list when the post has no reactions. Group: Posts. Billing per call: 1 Credits.

NameTypeReqDescription
countinteger–Number of results per page.
postIdstringyesThe post's `ugcPostId`, taken from `/person-profile/posts` or `/company/posts`. Use `ugcPostId` here, not `activityId`.
startinteger–Offset of the first result. Pass the `cursor` value from the previous response to fetch the next page.

No output schema declared.

No examples provided.

Common questions

What is the com.jojapi/linkedin MCP server?

com.jojapi/linkedin is an MCP server listed in the public MCP registry as com.jojapi/linkedin. LinkedIn: The LinkedIn Data API offers access to detailed information on individuals, companies. This page covers its hosted endpoint (https://mcp.jojapi.com/linkedin).

Is the com.jojapi/linkedin MCP server safe to use?

com.jojapi/linkedin scores 76 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.

What tools does the com.jojapi/linkedin MCP server expose?

com.jojapi/linkedin exposes 12 tools: get_person_profile, get_person_profile_posts, get_people_search, get_company, get_company_search, and 7 more. Their descriptions and schemas cost roughly 1,396 tokens of context every time the server is loaded.

Does the com.jojapi/linkedin MCP server require authentication?

No. We connected to com.jojapi/linkedin without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.jojapi/linkedin MCP server still maintained?

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