← All servers

ai-crawler-readiness

connects

shop.lumnika.com

Can AI crawlers read this site? GPTBot/ClaudeBot verdicts, robots vs edge blocking, 47k-domain index

https://shop.lumnika.com/ai-readiness/mcpWebsiteUnknownMCP 2025-06-18v1.0.0last checked 21 Oct 2026spoke MCP on 98.9% of 88 checks (30 days)initialize in 117 ms

Last checked 21 Oct 2026

  • ✓Answered the MCP handshake (MCP 2025-06-18)
  • –Auth scheme could not be determined
  • ✓Lists 5 tools
  • ✓No blockers or warnings
  • !Spoke MCP on 87 of 88 checks (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

–Claude CodeUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Claude Code docs · read on 2026-08-30

–Claude (claude.ai & Desktop)Unknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

–ChatGPTUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

ChatGPT docs · read on 2026-08-30

–CursorUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Cursor docs · read on 2026-08-30

–VS Code (Copilot)Unknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 21 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
Unknown
Protected-resource metadata
✕Not found

Without it a client has to guess where the authorization server lives.

Anonymous access
Refused — credentials required

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

domain_readinessedge_blockingmeasure_domainrecent_changesweb_openness

Contract history

20 Sep 2026v1.0.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for ai-crawler-readiness
[![MCP status](https://mcpi.app/servers/ai-crawler-readiness/badge.svg)](https://mcpi.app/servers/ai-crawler-readiness)