Docker MCP Registry · Public certification

Protected MCP runtime

The MCP remote is live, but unauthenticated initialize handshakes are currently blocked by auth.

Protected MCP runtime No active certification tier Health 65/100 Api Key Mcp Remote
Open badge SVG Proof JSON Registry detail Open endpoint

Trust summary

Endpoint POST /sse
Service Cloudflare Container
Last unpaid proof
Last paid proof Never
Current intent Unknown
Observed price n/a
Open findings 1
Active incidents 1

Proof levels

Level 1 confirms that the endpoint speaks MPP correctly before payment. Level 2 confirms that the registry actually paid the endpoint and received a successful response.

Level 1

Unpaid structural proof

Pending

This proof checks that the endpoint returns a valid unpaid MPP challenge and that the challenge can be parsed and normalized by the registry.

Latest outcomeAuth Required
Checked at
HTTP status401
Latency5 ms
Challenge count0
Fresh until
Primary challengen/a
Run idde76b4dd-2...92d8698872

Level 2

Paid delivery proof

Paid proof optional

This proof shows whether the registry actually paid the endpoint and received a successful post-payment response, using the stored receipt and payment reference as auditable evidence.

Latest outcomePending
Checked atNever
HTTP statusn/a
Latencyn/a
Billed amountn/a
Fresh untilNever
Payment referencen/a
Receipt statusUnknown
Receipt timestampNever
Response content typen/a
Response fingerprintn/a
Run idn/a

Badge and embed

Providers can embed this badge directly in docs, status pages, or changelogs. The link points back to this certification page so agents and humans can inspect the proof details.

IndexPay certification badge for Cloudflare Container
HTML embed
Markdown embed

Signals and findings

MCP remote is reachable, but initialize now requires authentication. Warning

Unpaid probe · 644 occurrence(s)

Workflow partially proven Info

The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.