# com.lumnika/ai-crawler-readiness (remote · shop.lumnika.com)

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

- Trust score: 33/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `shop.lumnika.com`: 33/100 (this document), [markdown](https://verifymcp.io/servers/com-lumnika-ai-crawler-readiness/ai-readiness-mcp.md), [page](https://verifymcp.io/servers/com-lumnika-ai-crawler-readiness/ai-readiness-mcp)

## Channel facts

- Endpoint: `https://shop.lumnika.com/ai-readiness/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the com.lumnika/ai-crawler-readiness MCP server?

com.lumnika/ai-crawler-readiness is a hosted endpoint at https://shop.lumnika.com/ai-readiness/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-lumnika-ai-crawler-readiness 'https://shop.lumnika.com/ai-readiness/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-lumnika-ai-crawler-readiness": {
      "url": "https://shop.lumnika.com/ai-readiness/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-lumnika-ai-crawler-readiness": {
      "type": "http",
      "url": "https://shop.lumnika.com/ai-readiness/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-lumnika-ai-crawler-readiness]
url = "https://shop.lumnika.com/ai-readiness/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-lumnika-ai-crawler-readiness": {
      "type": "remote",
      "url": "https://shop.lumnika.com/ai-readiness/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-lumnika-ai-crawler-readiness --url 'https://shop.lumnika.com/ai-readiness/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-lumnika-ai-crawler-readiness:
    url: "https://shop.lumnika.com/ai-readiness/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-lumnika-ai-crawler-readiness": {
      "Transport": "http",
      "Url": "https://shop.lumnika.com/ai-readiness/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-lumnika-ai-crawler-readiness -t streamable-http -u 'https://shop.lumnika.com/ai-readiness/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-lumnika-ai-crawler-readiness": {
      "type": "http",
      "url": "https://shop.lumnika.com/ai-readiness/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 33, −30)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Authorization: unverified → fail
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-20 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-19 (score 63)

First indexed and scored.

## MCP tools (5)

### `domain_readiness` (~180 tokens)

Can AI assistants actually read this domain? Returns the measured readiness score, the per-crawler verdict (served / blocked in robots.txt / refused by the edge despite robots.txt allowing it), and which edge vendor answers for the host. Measured with real HTTP requests, not guessed from robots.txt alone. Google-Extended and Applebot-Extended are robots.txt tokens, not crawlers: they are flagged robotsOnly, carry no server verdict, and are excluded from every count about what the server did. Also returns `fixes`: the ordered, domain-specific list of what to change to let the blocked crawlers in, separating what is written in the site own robots.txt from what the CDN/WAF applies on top of it.

Input parameters:

- `host` (string, required): A bare domain, e.g. "wikipedia.org" (no scheme, no path).

### `web_openness` (~53 tokens)

How much of the most-visited web is readable by AI assistants right now: the share of measured domains that block at least one AI crawler, and the served / robots-blocked / edge-blocked breakdown per crawler.

### `edge_blocking` (~144 tokens)

Who is actually doing the blocking: for each CDN/WAF vendor, the share of (domain x crawler) pairs that robots.txt ALLOWS and the server refuses anyway — i.e. how much of the blocking is an infrastructure default rather than a decision the site owner made. Each vendor also comes broken down per crawler, which separates a blanket wall (same rate for every crawler) from a managed block list that names some AI user-agents and not others.

Input parameters:

- `limit` (integer): How many vendors to return, highest contradiction rate first (default 12). Vendors with fewer than 200 allowed pairs are left out of the table rather than reported on thin evidence.

### `recent_changes` (~168 tokens)

What CHANGED: the domains that recently started or stopped blocking a specific AI crawler, with the day the flip was observed and whether it happened in robots.txt or at the edge. This cannot be reconstructed after the fact from any public source — it exists only because the index made the same requests the day before and the day after. Use it to answer 'who just blocked/unblocked ChatGPT, Claude, Perplexity...' or to watch one domain over time.

Input parameters:

- `days` (integer): Look-back window in days (default 30, max 365).
- `host` (string): Restrict to one domain, e.g. "nytimes.com" (optional).
- `limit` (integer): How many changes to return, most recent first (default 50, max 500).

### `measure_domain` (~149 tokens)

Measure a domain RIGHT NOW instead of reading the archive: 9 real HTTP requests, one from a browser user-agent and one per AI crawler user-agent, plus robots.txt / llms.txt / sitemap. Use it for any site the index has not reached yet, or when the caller wants a fresh verdict after changing robots.txt or a WAF rule. Returns the same `fixes` list as domain_readiness, derived from the fresh measurement.

Input parameters:

- `force` (boolean): Measure again even if the archive already has a verdict from the last 24 hours (default false).
- `host` (string, required): A bare domain, e.g. "wikipedia.org" (no scheme, no path).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-lumnika-ai-crawler-readiness/ai-readiness-mcp#diagnostics

## Score history

- 2026-09-21: 33
- 2026-09-20: 63
- 2026-09-19: 63

## Common questions

### What is the com.lumnika/ai-crawler-readiness MCP server?

com.lumnika/ai-crawler-readiness is an MCP server listed in the public MCP registry as com.lumnika/ai-crawler-readiness. Can AI crawlers read this site? GPTBot/ClaudeBot verdicts, robots vs edge blocking, 47k-domain index. This page covers its hosted endpoint (https://shop.lumnika.com/ai-readiness/mcp).

### Is the com.lumnika/ai-crawler-readiness MCP server safe to use?

com.lumnika/ai-crawler-readiness scores 33 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the com.lumnika/ai-crawler-readiness MCP server expose?

com.lumnika/ai-crawler-readiness exposes 5 tools: domain_readiness, web_openness, edge_blocking, recent_changes, measure_domain. Their descriptions and schemas cost roughly 694 tokens of context every time the server is loaded.

### Does the com.lumnika/ai-crawler-readiness MCP server require authentication?

Yes. com.lumnika/ai-crawler-readiness asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the com.lumnika/ai-crawler-readiness MCP server still maintained?

com.lumnika/ai-crawler-readiness is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://shop.lumnika.com/ai-readiness/mcp
- Website: https://shop.lumnika.com/ai-readiness/
- Changelog RSS feed: https://verifymcp.io/servers/com-lumnika-ai-crawler-readiness/ai-readiness-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-lumnika-ai-crawler-readiness/ai-readiness-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-lumnika-ai-crawler-readiness/ai-readiness-mcp