MCP server health, State of MCP census
Splunk Observability
io.github.signalfx/splunk-o11y-mcp-connect
Splunk Observability Cloud MCP server: traces, metrics, alerts, and dashboards for IDEs.
- remote_unreachable
Checks
The exact rows akashi check io.github.signalfx/splunk-o11y-mcp-connect 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 | pass | exists |
| repo freshness | pass | pushed 6d ago |
| remote reachable | fail | unreachable |
| at least one live entrypoint | pass | 1 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
Packages
No packages declared.
Remote endpoints
- https://api.{realm}.signalfx.com/v2/mcp
streamable-http · unreachable
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 io.github.signalfx/splunk-o11y-mcp-connectInstall 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.signalfx/splunk-o11y-mcp-connect --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.