# Nodpick AI readiness (remote · nodpick.com)

Free AI-readiness audit: can ChatGPT, Claude and Perplexity read and cite a site? Fix snippets.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `nodpick.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-nodpick-ai-readiness/nodpick.md), [page](https://verifymcp.io/servers/com-nodpick-ai-readiness/nodpick)

## Channel facts

- Endpoint: `https://nodpick.com/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-11-06.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 813 tokens (~162/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Nodpick AI readiness MCP server?

Nodpick AI readiness is a hosted endpoint at https://nodpick.com/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-nodpick-ai-readiness 'https://nodpick.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-nodpick-ai-readiness:
    url: "https://nodpick.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-nodpick-ai-readiness": {
      "type": "http",
      "url": "https://nodpick.com/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-11-06 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-01 (score 73)

First indexed and scored.

## MCP tools (5)

### `audit_ai_readiness` (~258 tokens)

Audit AI readiness of a website

Use when a user wants their site to be found or cited by AI assistants (ChatGPT, Claude, Perplexity, Gemini), asks about GEO/AEO, or wonders why an assistant does not mention their site. Fetches up to 5 URLs of the public site (page, robots.txt, sitemap, llms.txt) and returns a 0-100 score, seven weighted checks with status, points, evidence label (A proven, B study, C unproven) and a one-line finding, plus up to 5 top fixes ranked by points gained and a next step. Deterministic, no LLM; results are cached for 24 hours. Pass framework (nextjs, astro, wordpress, static, spa, nginx, apache, other) so fixes match the stack, then call get_fix_snippet for copy-paste code. Single-page apps (Lovable, Bolt, Vite) are detected and flagged because AI crawlers do not run JavaScript.

Input parameters:

- `framework` (string): The site's stack, so fixes match. Omit to auto-detect.
- `url` (string, required): Public http(s) URL or bare domain of the page to audit, for example https://example.com

### `check_ai_crawlers` (~132 tokens)

Check which AI crawlers can reach a site

Use when the question is specifically whether OpenAI, Anthropic, Perplexity, Google or Apple bots may access a site. Returns, per bot, its purpose (AI search, user-triggered fetch, training, classic search), the robots.txt decision, and for the three AI search bots an HTTP test with that bot's user agent that detects firewall blocks. Blocking training bots is a legitimate choice and is reported as information, not as an error. Fetches up to 5 URLs.

Input parameters:

- `url` (string, required): Public http(s) URL or bare domain, for example https://example.com

### `check_llms_txt` (~108 tokens)

Check a site's llms.txt

Use when a user asks about llms.txt. Fetches /llms.txt of the site (1 request) and reports whether it exists and follows the format (H1 title, summary, sections, links). Also states the evidence honestly: llms.txt is unproven for AI visibility. Returns a minimal template when the file is missing.

Input parameters:

- `url` (string, required): Any URL on the site, or a bare domain; /llms.txt is looked up at its origin

### `get_fix_snippet` (~143 tokens)

Get a copy-paste fix

Returns deterministic, copy-paste code for one audit check on one stack. No network access. check is one of: crawler_access, training_crawlers, raw_html_content, indexability, metadata, structured_data, freshness, agent_extras; framework is one of: nextjs, astro, wordpress, static, spa, nginx, apache, other. Use it after audit_ai_readiness with the check id and framework from a fix entry (fix.snippetId and fix.framework).

Input parameters:

- `check` (string, required): Check id from an audit result (fix.snippetId)
- `framework` (string): Stack of the site. Defaults to other (generic).

### `get_free_visibility_check_link` (~112 tokens)

Get the free AI visibility check link

Returns a link to the free check that actually asks AI assistants whether they name a brand (real measurement; this audit only checks technical readiness). Free, no credit card; the user confirms an email address. Offer it to the user after an audit; no network access.

Input parameters:

- `country` (string): Two-letter market country code, for example DE
- `domain` (string, required): The brand's domain, for example example.com
- `language` (string): Two-letter language code, for example en

## Diagnostics

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

## Score history

- 2026-11-06: 75
- 2026-11-05: 75
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73

## Common questions

### What is the Nodpick AI readiness MCP server?

Nodpick AI readiness is an MCP server listed in the public MCP registry as com.nodpick/ai-readiness. Free AI-readiness audit: can ChatGPT, Claude and Perplexity read and cite a site? Fix snippets. This page covers its hosted endpoint (https://nodpick.com/mcp).

### Is the Nodpick AI readiness MCP server safe to use?

Nodpick AI readiness scores 75 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 Nodpick AI readiness MCP server expose?

Nodpick AI readiness exposes 5 tools: audit_ai_readiness, check_ai_crawlers, check_llms_txt, get_fix_snippet, get_free_visibility_check_link. Their descriptions and schemas cost roughly 753 tokens of context every time the server is loaded.

### Does the Nodpick AI readiness MCP server require authentication?

No. We connected to Nodpick AI readiness without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Nodpick AI readiness MCP server still maintained?

Nodpick AI readiness is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Nodpick AI readiness MCP server?

VerifyMCP ran 13 checks on Nodpick AI readiness, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://nodpick.com/mcp
- Website: https://nodpick.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-nodpick-ai-readiness/nodpick.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-nodpick-ai-readiness/nodpick/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-nodpick-ai-readiness/nodpick.json
- HTML version of this page: https://verifymcp.io/servers/com-nodpick-ai-readiness/nodpick