pulsemcp verified Safe content atomic mcp-remote

LinkedIn Posts Hunter

LinkedIn Posts Hunter MCP provides AI-powered LinkedIn job post search and tracking through Playwright browser automation with persistent authentication, local SQLite storage, and a React dashboard interface. Built by Kevin Weitgenant, it automates LinkedIn post scraping with configurable pagination and concurrency, stores all data locally for complete privacy, and offers dual control through natural language AI commands or a modern web UI with advanced filtering by keywords, application status, dates, and post IDs. The implementation features automatic authentication detection, concurrent post processing with metadata extraction (author details, engagement metrics, timestamps), and a responsive dashboard with both table and card views that auto-polls for updates, making it valuable for job seekers who want to systematically track and manage LinkedIn opportunities without relying on external services.

Cognium trust score

88%

Tier

Verified

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-28.

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

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: database
Source: PulseMCP
Repository: github.com/kevin-weitgenant/linkedin-posts-hunter-mcp-server
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve LinkedIn Posts Hunter 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"