Remote MCP · Endpoint

ContentIn — LinkedIn Ghostwriter MCP server

No — it is up, but it requires credentials. ContentIn — LinkedIn Ghostwriter answered 1 hour ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 hour ago

Server URL

https://mcp.contentin.io/mcp-server

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
io.contentin/linkedin
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
11 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Write LinkedIn posts in your voice: ideas, drafts, scheduling, analytics from your personal AI.
Website
https://contentin.io/linkedin-mcp-server/
Listing
From the official MCP registry (active).
Recent checks of ContentIn — LinkedIn Ghostwriter
CheckedResultHandshake
1 hour agoCredentials required—
1 day agoHandshake completed613 ms
2 days agoHandshake completed102 ms
3 days agoHandshake completed103 ms
4 days agoHandshake completed94 ms
5 days agoHandshake completed131 ms
6 days agoHandshake completed131 ms
9 days agoHandshake completed98 ms
11 days agoHandshake completed233 ms
14 days agoHandshake completed94 ms
16 days agoHandshake completed131 ms
18 days agoHandshake completed140 ms
20 days agoHandshake completed176 ms
22 days agoHandshake completed121 ms
24 days agoHandshake completed84 ms
26 days agoHandshake completed88 ms
27 days agoHandshake completed111 ms
28 days agoHandshake completed80 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with ContentIn — LinkedIn Ghostwriter and makes no claim about it beyond what these checks measured.