MCP server health, State of MCP census

ITEON MCP Server

pl.iteon/mcp

Polski software house B2B: 5 public + 7 OAuth 2.1 private MCP tools (AI estimate, draft, risk).

degraded checked 2026-07-02 · 7/9 checks passed · keyless
  • repo_404

Checks

The exact rows akashi check pl.iteon/mcp prints, from the 2026-07-02 census.

CheckStatusDetail
registry statuspassactive
server.json validpassvalidates against its declared JSON Schema
repo reachablefail404 (repository gone)
remote reachablepassHTTP 403 via initialize
MCP conformancewarnauth-gated (HTTP 403): alive, not verifiable keyless
remote reachablepassHTTP 200 via initialize
MCP conformancepassinitialize handshake ok
tools/listpass5 tools: methodology.lookup, case_studies.find_relevant, expert_match.find, stack.health_audit, system.status
at least one live entrypointpass2 alive

Evidence

Repository

github · missing· HTTP 404

https://github.com/ITEONpl/iteon-apps

Packages

No packages declared.

Remote endpoints

server.json

validagainst its declared schema

One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).

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 pl.iteon/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 pl.iteon/mcp --badge.

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