Arclan / Servers

www-linkedin-com-pulse-mcp-vs-apify-custom-agents-when-use-each-marek-cziba-rltzf

https://www.linkedin.com/pulse/mcp-vs-apify-custom-agents-when-use-each-marek-cziba-rltzf/

auth_gated Not production-safe Score 36/100 unknown auth required

At a glance

Endpointhttps://www.linkedin.com/pulse/mcp-vs-apify-custom-agents-when-use-each-marek-cziba-rltzf/
Sourcehttps://github.com/MarekCziba/mcp-servers
Transportunknown
Tools0
Authbearer (bearer)
First seen2026-09-30 19:16:18
Last checked2026-11-11 19:18:20

Observed reliability

7-day uptime0%
24-hour uptime—
Handshake success0%
Latency p50 / p950 / 0 ms
Last successful check—

Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →

Validation history

CheckedReachableHandshakeLatencyScoreState
2026-11-11 19:18:20✓✗0 ms35auth_gated
2026-11-04 19:18:16✓✗0 ms35auth_gated
2026-10-28 19:17:54✓✗0 ms35auth_gated
2026-10-21 19:17:32✓✗0 ms35auth_gated
2026-10-14 19:17:13✓✗0 ms35auth_gated
2026-10-07 19:16:34✓✗0 ms35auth_gated
2026-09-30 19:16:25✓✗0 ms35auth_gated

Query this programmatically

Agents can pull this record live over the MCP protocol or REST:

get_server("https://www.linkedin.com/pulse/mcp-vs-apify-custom-agents-when-use-each-marek-cziba-rltzf/")   # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/www-linkedin-com-pulse-mcp-vs-apify-custom-agents-when-use-each-marek-cziba-rltzf   # JSON