MCP server health, State of MCP census

IntentWake Audience Intelligence

com.intentwake/intentwake

Enrich first-party lists with live intent, activity, and inbox signals for marketing and outreach.

healthy checked 2026-09-13 · 5/7 checks passed · keyless

Checks

The exact rows akashi check com.intentwake/intentwake prints, from the 2026-09-13 census.

CheckStatusDetail
registry statuspassactive
server.json validpassvalidates against its declared JSON Schema
repo reachableskipno repository declared
package npmpasspublished (0.2.3)
remote reachablepassHTTP 401 via initialize
MCP conformancewarnauth-gated (HTTP 401): alive, not verifiable keyless
at least one live entrypointpass2 alive

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

No repository declared.

Packages

  • npm @intentwake/mcp · published(0.2.3)

Remote endpoints

server.json

validagainst its declared schema

One of 31538 servers in the 2026-09-13 State of MCP census: 25411 healthy (80.6%), 4667 degraded (14.8%), 1184 dead (3.8%), 276 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.intentwake/intentwake

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

Prefer the data? This page has a machine-readable record carrying the same checks, verdict and census date, under the same methodology.

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.intentwake/intentwake --badge.

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