Nodpick AI readiness
REMOTE · NODPICK.COM
Free AI-readiness audit: can ChatGPT, Claude and Perplexity read and cite a site? Fix snippets.
Available components
Last scanned (7 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://nodpick.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nodpick.com | CN=YE2,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6a7172367d0efa38766cd51f4fdc0bc1ea3 |
| SANs: *.nodpick.com, nodpick.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nodpick.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nodpick.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://cdn.paddle.com https://sandbox-cdn.paddle.com; style-src 'self' 'unsafe-inline' https://cdn.paddle.com https://sandbox-cdn.paddle.com; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://*.paddle.com; frame-src https://buy.paddle.com https://sandbox-buy.paddle.com; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self "https://buy.paddle.com" "https://sandbox-buy.paddle.com") |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nodpick.com/mcp | Verified | 200 | |
| http (plaintext) | http://nodpick.com/mcp | HTTPS enforced | 308 | https://nodpick.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_ai_readiness Audit AI readiness of a website ~258
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.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | The site's stack, so fixes match. Omit to auto-detect. |
| url | string | yes | Public http(s) URL or bare domain of the page to audit, for example https://example.com |
No output schema declared.
No examples provided.
check_ai_crawlers Check which AI crawlers can reach a site ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) URL or bare domain, for example https://example.com |
No output schema declared.
No examples provided.
check_llms_txt Check a site's llms.txt ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Any URL on the site, or a bare domain; /llms.txt is looked up at its origin |
No output schema declared.
No examples provided.
get_fix_snippet Get a copy-paste fix ~143
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).
| Name | Type | Req | Description |
|---|---|---|---|
| check | string | yes | Check id from an audit result (fix.snippetId) |
| framework | string | – | Stack of the site. Defaults to other (generic). |
No output schema declared.
No examples provided.
get_free_visibility_check_link Get the free AI visibility check link ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter market country code, for example DE |
| domain | string | yes | The brand's domain, for example example.com |
| language | string | – | Two-letter language code, for example en |
No output schema declared.
No examples provided.
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.
remote · nodpick.com
claude mcp add --transport http com-nodpick-ai-readiness 'https://nodpick.com/mcp'
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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.