MCP server health, State of MCP census

Slack ↔ WxO MCP Gateway

io.github.markusvankempen/slack-wxo-mcp-gateway

Lifts WxO Slack limits: every-message wake-up, multi-channel MCP. https://markusvankempen.github.io/

healthy checked 2026-07-22 · 7/7 checks passed · keyless

Checks

The exact rows akashi check io.github.markusvankempen/slack-wxo-mcp-gateway prints, from the 2026-07-22 census.

Check	Status	Detail
registry status	pass	active
server.json valid	pass	validates against its declared JSON Schema
repo reachable	pass	exists
repo freshness	pass	pushed 4d ago
package npm	pass	published (1.0.3)
at least one live entrypoint	pass	2 alive
license present	pass	Apache-2.0

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 · alive

https://github.com/markusvankempen/slack-wxo-mcp-gateway

Packages

npm @markusvankempen/slack-wxo-mcp-gateway · published(1.0.3)

Remote endpoints

No remote endpoint declared.

server.json

validagainst its declared schema

One of 18032 servers in the 2026-07-22 State of MCP census: 14367 healthy (79.7%), 2850 degraded (15.8%), 724 dead (4.0%), 91 unknown (0.5%).

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 io.github.markusvankempen/slack-wxo-mcp-gateway

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 io.github.markusvankempen/slack-wxo-mcp-gateway --badge.

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