Remote MCP · Endpoint

Linkedin_ads MCP server

No. Linkedin_ads answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/linkedin_ads/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/linkedin_ads
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
400 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
LinkedIn Ads MCP Pack
Website
https://pipeworx.io/packs/linkedin_ads
Repository
https://github.com/pipeworx-io/mcp-linkedin_ads
Listing
From the official MCP registry (active).
Recent checks of Linkedin_ads
CheckedResultHandshake
1 hour agoHandshake completed400 ms
2 days agoHandshake completed75 ms
4 days agoHandshake completed52 ms
5 days agoHandshake completed77 ms
7 days agoHandshake completed56 ms
8 days agoHandshake completed185 ms
9 days agoHandshake completed46 ms
12 days agoHandshake completed43 ms
14 days agoHandshake completed57 ms
15 days agoHandshake completed84 ms
17 days agoHandshake completed532 ms
18 days agoHandshake completed37 ms
19 days agoHandshake completed208 ms
20 days agoHandshake completed37 ms
20 days agoHandshake completed50 ms
22 days agoHandshake completed59 ms
23 days agoHandshake completed48 ms

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

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 Linkedin_ads and makes no claim about it beyond what these checks measured.