mcp-registry/com.gtmotto/linkedin · v1.2.0
As of 2026-10-26 20:16 UTC, the Gtmotto LinkedIn MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 2 minutes.
Self-driving LinkedIn prospecting: it sources, warms and invites daily. You approve every message.
Point your MCP client at this streamable-http endpoint: https://agent.gtmotto.com/mcp
2 tool definition(s) exceed ~1,200 tokens each (largest: gtm_create_play, ~1,766).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,788 tokens every session. How to fix →
9 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Handshake + tools/list takes ~1,926 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.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. 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.gtmotto/linkedin"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.gtmotto/linkedin"}) over MCP.
gtm_create_play ~1,766 tokensgtm_configure_source ~1,222 tokensgtm_update_play ~462 tokensgtm_forget_harvested_posts ~411 tokensgtm_preview_source ~409 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.gtmotto%2Flinkedin?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.gtmotto%2Flinkedin?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.gtmotto%2Flinkedin.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.gtmotto%2Flinkedin.svg :target: https://glimind.com/server/mcp-registry%2Fcom.gtmotto%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:1284415bc8327b48…, first seen 2026-10-17, included at leaf 15131 of 75,257. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable data servers · most reliable knowledge 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-26 20:16 UTC, the Gtmotto LinkedIn MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 2 minutes.
Gtmotto LinkedIn MCP server advertises 21 tools, including gtm_approve, gtm_configure_source, gtm_connect_linkedin, gtm_create_play, gtm_estimate_icp.
Point your MCP client at this streamable-http endpoint: https://agent.gtmotto.com/mcp
Glimind scanned all 21 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.