com.glitchexecutor.grow/glitch-grow-linkedin-ad-mcp
com.glitchexecutor.grow/glitch-grow-linkedin-ad-mcp
Is the com.glitchexecutor.grow/glitch-grow-linkedin-ad-mcp MCP server down? Yes. It has given no valid answer since 2026-10-20: not found.
MCP server for the LinkedIn Marketing API — campaigns, analytics, creatives.
not found down since 2026-10-20 · probed 2026-11-15 · unchanged since 2026-10-27
error: No solution found when resolving dependencies cause: Because glitch-grow-linkedin-ad-mcp was not found in the package registry and you require glitch-g
- Run it
- uvx glitch-grow-linkedin-ad-mcp@0.1.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/glitch-exec-labs/glitch-grow-linkedin-ad-mcp
- Registry
- active, updated 2026-05-07 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- com.files/python-mcp · crashed on start
- Flieber com.flieber/flieber · crashed on start
- focxle — what your AI agents cost com.focxle/spend · install failed
- com.getsingularis/singularis · alive
- gnomancer com.gnomancer/gnomancer · alive
- GRAFOMEM CGR Capture com.grafomem/cgr-capture · crashed on start
- Graqle com.graqle/graqle · crashed on start
- com.hodlodds/hodlodds-mcp · crashed on start
Servers that mention linkedin.
- Adako: ad ops for AI assistants ai.adako/ads · needs auth
- ai.adside/adside · needs auth
- Autoposting ai.autoposting/autoposting · not MCP
- BAMF.ai ai.bamf/bamf · not MCP
- Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram ai.bowmark/bowmark · alive
- LinkedIn MCP Server ai.com.mcp/linkedin · not MCP
- DataForB2B ai.dataforb2b/dataforb2b · needs auth
- FeedBoss ai.feedboss/feedboss · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-20, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.