MCP server health, State of MCP census

LinkedIn MCP Server (Salesbot)

cz.salesbot/linkedin-mcp-server

Human-in-the-loop LinkedIn outreach and a built-in sales CRM for AI agents. Safety-gated, anti-spam.

healthy checked 2026-07-02 · 9/9 checks passed · keyless

Checks

The exact rows akashi check cz.salesbot/linkedin-mcp-server prints, from the 2026-07-02 census.

CheckStatusDetail
registry statuspassactive
server.json validpassvalidates against its declared JSON Schema
repo reachablepassexists
repo freshnesspasspushed 13d ago
remote reachablepassHTTP 200 via initialize
MCP conformancepassinitialize handshake ok
tools/listpass45 tools: search_linkedin_people, search_google_xray, enrich_contacts, search_linkedin_navigator, get_contact_profile, list_contacts, list_campaigns, add_contacts_to_campaign, ...
at least one live entrypointpass2 alive
license presentpassMIT

Evidence

Packages

No packages declared.

Remote endpoints

  • https://app.salesbot.cz/api/mcp

    streamable-http · reachable· HTTP 200· initialize_ok

    45 tools: search_linkedin_people, search_google_xray, enrich_contacts, search_linkedin_navigator, get_contact_profile, list_contacts, list_campaigns, add_contacts_to_campaign, ...

server.json

validagainst its declared schema

One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).

Verify it yourself

This page is a static read of one dated probe. Run the same check locally, any time, with no key:

$ akashi check cz.salesbot/linkedin-mcp-server

Install Akashi - single Go binary, zero keys, MIT licensed.

Is this your server?

Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check cz.salesbot/linkedin-mcp-server --badge.

Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.