The GTM MCP Directory
Directory / Data & Enrichment / LinkupAPI LinkedIn Skills

LinkupAPI LinkedIn Skills

Community MCP Gate unknown Data & Enrichment RESEARCHED Checked 2026-09-12
RESEARCHED Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: linkupapi.com · entry id 01-linkupapi-linkedin-skills · source 01-data-enrichment.md line 2817

What it does
Claude Skills for LinkedIn outreach, high-intent leads, feed engagement, and profile enrichment via LinkupAPI MCP.
AI features, separated from automation with an AI label on it
Homepage copy mentions AI/ML-related terms; specific AI feature list not independently verified beyond that mention this pass. See sources.
RevOps role
Upstream contact/company data or enrichment utility feeding CRM and outbound tooling
MCP server
Status bucket
Community MCP
Auth
not recorded
Parsed URLs
1 found in the mcp_url field
Endpoint probe
not probed yet

A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing. The status was established on 2026-09-12 and the MCP URL has not been probed live yet.

mcp_status, verbatim from the file:

community

mcp_url, verbatim from the file:

https://github.com/claude-dev-code/claude-skills-linkedin

What this server exposes

Not harvested yet. Unmeasured, not empty: nobody has read this server's tool list, so this page says nothing about what it exposes.

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. The full roll up is on the tools index.

Command line

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

Access gate
Gate bucket
Gate unknown
Can a solo operator reach it
Not established

api_gate, verbatim from the file:

unknown

949 of 1252 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess.

API documentation

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

GitHub health

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

On GitHub

No GitHub organisation could be tied to linkupapi.com with evidence on 2026-09-15.

Recorded by the harvest: not checked: gh CLI missing or not logged in.

Jobs it can do

No job tag on this entry.

981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag.

Sources

3 source URLs. Raw sources field, verbatim:

https://linkupapi.com, https://linkupapi.com/llms.txt, https://github.com/claude-dev-code/claude-skills-linkedin

Notes, verbatim from the file
API mentioned on https://linkupapi.com/llms.txt; pricing/gate not inferred from presence alone. mcp_status=community from discovery source github-mcp-server-topic; mcp_url is the listed package/repo URL, not an official vendor MCP claim. api_gate unknown with dated probe 2026-09-12; free/paid not inferred from HTTP status alone. Promote wave N 2026-09-12: canonical name LinkupAPI LinkedIn Skills (draft listed as claude-dev-code/claude-skills-linkedin). Category corrected from email-deliverability to data-enrichment.
Provenance
Entry id
01-linkupapi-linkedin-skills
Source file
01-data-enrichment.md
Source line
2817
Tier
RESEARCHED
last_checked
2026-09-12
Data baked
2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.