pulsemcp scanned Safe content atomic mcp-remote

Linked API

This MCP server provides comprehensive access to LinkedIn automation and data extraction through the Linked API service. Built with TypeScript and the Model Context Protocol SDK, it offers 25+ tools covering standard LinkedIn operations (messaging, connections, posts, searches) and Sales Navigator functionality, with built-in support for background workflow processing that keeps clients responsive during long-running operations. The implementation handles authentication via API tokens, includes progress tracking for multi-minute LinkedIn workflows, and provides both HTTP and stdio transport options with Docker deployment support. Designed for sales professionals, recruiters, and developers building LinkedIn automation workflows, it enables use cases like lead generation, relationship management, content engagement, and data extraction without directly interfacing with LinkedIn's complex automation requirements.

Cognium trust score

64%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-02.

Scan details: Circle-IR · 2026-09-02 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: cloud-infra
Source: PulseMCP
Repository: github.com/linked-api/linkedapi-mcp
Author type: human
Last scanned: 2026-09-02
Updated: 2026-09-02

View source Find related skills

MCP

Resolve Linked API from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"