MCP server health, State of MCP census

Glitch Grow Linkedin Ad Mcp

com.glitchexecutor.grow/glitch-grow-linkedin-ad-mcp

MCP server for the LinkedIn Marketing API — campaigns, analytics, creatives.

dead checked 2026-08-03 · 2/5 checks passed · keyless

repo_404
pypi_missing

Checks

The exact rows akashi check com.glitchexecutor.grow/glitch-grow-linkedin-ad-mcp prints, from the 2026-08-03 census.

Check	Status	Detail
registry status	pass	active
server.json valid	pass	validates against its declared JSON Schema
repo reachable	fail	404 (repository gone)
package pypi	fail	glitch-grow-linkedin-ad-mcp not found
at least one live entrypoint	fail	nothing installable or reachable

Spec 2026-07-28 readiness

No runtime readiness verdict: this server has no keylessly reachable conformant MCP endpoint (package-only, auth-gated, or down at census time), so its behavior against the 2026-07-28 revision cannot be measured without credentials. Absence of evidence is recorded as absence, never guessed. Ecosystem numbers: the readiness report.

Evidence

Repository

github · missing· HTTP 404

https://github.com/glitch-exec-labs/glitch-grow-linkedin-ad-mcp

Packages

pypi glitch-grow-linkedin-ad-mcp · missing

Remote endpoints

No remote endpoint declared.

server.json

validagainst its declared schema

One of 19804 servers in the 2026-08-03 State of MCP census: 15974 healthy (80.7%), 2792 degraded (14.1%), 851 dead (4.3%), 187 unknown (0.9%).

Verify it yourself

This page is a static read of one dated probe. Run the same check locally, any time, with no key:

$ akashi check com.glitchexecutor.grow/glitch-grow-linkedin-ad-mcp

Install Akashi - single Go binary, zero keys, MIT licensed.

Is this your server?

Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check com.glitchexecutor.grow/glitch-grow-linkedin-ad-mcp --badge.

Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.