mcp-registry/com.reachmcp/linkedin · v0.1.0
As of 2026-10-18 09:14 UTC, the Reachmcp LinkedIn MCP server is up (it requires sign-in) with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
LinkedIn for AI agents: inbox, invitations, Sales Navigator search, posts. Quotas and webhooks.
Claude Code
claude mcp add --transport http reachmcp-linkedin-mcp-server https://app.reachmcp.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"reachmcp-linkedin-mcp-server": {
"type": "http",
"url": "https://app.reachmcp.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
58 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
Loading this server's tool list costs an agent ~14,844 tokens before any work — more than 90% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~2,106 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.reachmcp/linkedin"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.reachmcp/linkedin"}) over MCP.
salesnav_build_search_url ~1,149 tokensupdate_account_quotas ~706 tokenscreate_job ~675 tokensupdate_webhook_endpoint ~390 tokensreact_message ~379 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.reachmcp%2Flinkedin?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.reachmcp%2Flinkedin?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.reachmcp%2Flinkedin.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.reachmcp%2Flinkedin.svg :target: https://glimind.com/server/mcp-registry%2Fcom.reachmcp%2Flinkedin?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e63cdc9c444cf5e6…, first seen 2026-10-17, included at leaf 6641 of 21,313. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable other servers · most reliable media servers · most reliable web servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 09:14 UTC, the Reachmcp LinkedIn MCP server is up (it requires sign-in) with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
Reachmcp LinkedIn MCP server advertises 58 tools, including accept_invitation, archive_conversation, cancel_job, comment_post, connect.
Point your MCP client at this streamable-http endpoint: https://app.reachmcp.com/mcp
Glimind scanned all 58 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.