Preferly
REMOTE · WWW.PREFERLY.AI
Free AI visibility checks for any website: AI crawler access, llms.txt, schema, business info.
Available components
Last scanned (14 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 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. 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. 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1158 tokens (~193/item across 6 items; 6 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 Management23
- Stability observed for 7 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
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 18 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.
- 16 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.
- 15 Nov 26 0
- Tool “check_ai_crawler_access” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 14 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 21 Nov 2026 · Probed https://www.preferly.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.preferly.ai | CN=YR1,O=Let's Encrypt,C=US | 20 Nov 2026 | 18 Feb 2027 | RSA 2048 | SHA256-RSA | 6b2b9fa14e4c31b12c2a1fd5aed886cf541 |
| SANs: *.preferly.ai, preferly.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.preferly.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| preferly.ai. | No DS | 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=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.preferly.ai/mcp | Verified | 200 | |
| http (plaintext) | http://www.preferly.ai/mcp | HTTPS enforced | 308 | https://www.preferly.ai/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 →
check_ai_crawler_access Check AI crawler access ~239
Use this when the user wants to know whether AI crawlers and AI tools can access a specific website. It reads the site's robots.txt and reports, for 10+ AI crawlers (including GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot and Google-Extended), whether each is allowed or blocked and which rule decides it. It also reports whether the homepage loads for an automated visitor or shows a bot check (such as Cloudflare, SiteGround or AWS WAF), whether the site publishes /llms.txt, and which schema.org types the homepage declares. Input: one public website address. It fetches only robots.txt, the homepage and /llms.txt, identifying itself as PreferlyBot, and changes nothing on the site. A result for the same domain may come from a check run in the last 10 minutes. It does not report what AI tools say about the business, search rankings, or pages other than the homepage.
| Name | Type | Req | Description |
|---|---|---|---|
| website | string | yes | The public website to check, like example.com or https://www.example.com. One site per call. |
| Name | Type | Req | Description |
|---|---|---|---|
| crawlers | array | yes | – |
| domain | string | yes | – |
| homepage | object | yes | – |
| learnMore | object | yes | – |
| llmsTxt | string | yes | – |
| nextSteps | array | yes | – |
| notChecked | string | yes | – |
| robotsTxt | object | yes | – |
| structuredData | array | yes | schema.org types declared on the homepage |
| summary | string | yes | – |
| verdict | string | yes | – |
No examples provided.
check_business_info Check readable business info ~142
Use this when the user asks whether AI tools can read a business's details from its website. It reports whether the business name, phone number, email, address, opening hours and prices are readable as text in the page, only appear after scripts run, or weren't found, on the homepage and up to 2 contact, booking or pricing pages that robots.txt allows. Input: one public website. Reads robots.txt, the homepage, /llms.txt and up to 2 more pages as PreferlyBot; changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| website | string | yes | The public website to check, like example.com or https://www.example.com. One site per call. |
No output schema declared.
No examples provided.
check_business_schema Check business structured data ~142
Use this when the user asks whether a website's structured data (schema.org JSON-LD) describes the business correctly. It reads the homepage's JSON-LD and reports the business type it found (Organization, LocalBusiness or a subtype), which business fields are present, missing or look off (name, url, phone, address, hours and more), and where the structured data and the page disagree. Input: one public website. Reads robots.txt, the homepage and /llms.txt as PreferlyBot; changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| website | string | yes | The public website to check, like example.com or https://www.example.com. One site per call. |
No output schema declared.
No examples provided.
check_llms_txt Check llms.txt ~153
Use this when the user asks whether a website has an llms.txt file or whether it's set up correctly. It fetches /llms.txt and reports whether it was found, its size and title, and every place it doesn't follow the llmstxt.org format (missing H1, no summary line, links that aren't Markdown or https), with line numbers. It also lists the homepage's main pages, which can seed a new llms.txt. Input: one public website. Reads robots.txt, the homepage and /llms.txt as PreferlyBot; changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| website | string | yes | The public website to check, like example.com or https://www.example.com. One site per call. |
No output schema declared.
No examples provided.
generate_ai_robots_txt Generate AI robots.txt lines ~161
Use this when the user wants robots.txt lines that control which AI crawlers may read their website. By default it lets AI search and assistant crawlers in (so the site can appear in AI answers) and keeps AI training crawlers out; either can be switched. Optional paths are kept private from every allowed crawler. It returns the lines to paste into robots.txt and which crawlers each group covers. It fetches nothing and needs no website.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_search | boolean | – | Let AI search and assistant crawlers in (default true). |
| allow_training | boolean | – | Let AI training crawlers in (default false). |
| disallow_paths | array | – | Paths every allowed crawler should skip, like ["/admin", "/cart"]. |
No output schema declared.
No examples provided.
quick_ai_visibility_check Quick AI visibility check ~236
Use this when the user asks what AI assistants say about a specific business, or whether AI tools mention or recommend it. Given the business's public website, it reads the site (robots.txt, the homepage and up to 2 contact, booking or pricing pages), writes 3 typical customer questions, and asks 3 AI models each question, answering from what they already know (no web search). It reports, for each model, whether it named the business and where it ranked when it gave a list, up to 2 statements where an AI model contradicts the website, and a one-line crawler summary. Input: one public website and, optionally, the business name. A result for the same website may come from a check run in the last 24 hours. Changes nothing on the site.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | – | The business's name, if the website doesn't make it obvious. |
| city | string | – | The city the business serves, if the website doesn't say. |
| website | string | yes | The public website to check, like example.com or https://www.example.com. One site per call. |
| Name | Type | Req | Description |
|---|---|---|---|
| cached | boolean | – | True when this is a recent check's result, served again |
| checkedAt | string | – | When the models were asked (UTC) |
| contradictions | array | – | Statements where an AI model contradicts the website |
| crawlerSummary | string | – | – |
| domain | string | yes | – |
| links | object | yes | Links to pages on www.preferly.ai |
| models | array | – | – |
| previewLabel | string | – | – |
| status | string | yes | partial: 2 of 3 models answered |
| tool | string | yes | – |
No examples provided.
How do I install the Preferly MCP server?
Preferly is a hosted endpoint at https://www.preferly.ai/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 · www.preferly.ai
claude mcp add --transport http ai-preferly-preferly 'https://www.preferly.ai/mcp'
What is the Preferly MCP server?
Preferly is an MCP server listed in the public MCP registry as ai.preferly/preferly. Free AI visibility checks for any website: AI crawler access, llms.txt, schema, business info. This page covers its hosted endpoint (https://www.preferly.ai/mcp).
Is the Preferly MCP server safe to use?
Preferly scores 76 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 Preferly MCP server expose?
Preferly exposes 6 tools: check_ai_crawler_access, check_llms_txt, check_business_schema, check_business_info, generate_ai_robots_txt, quick_ai_visibility_check. Their descriptions and schemas cost roughly 1,073 tokens of context every time the server is loaded.
Does the Preferly MCP server require authentication?
No. We connected to Preferly without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Preferly MCP server still maintained?
Preferly is still listed as active in the MCP registry. We last reached this channel on 21 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 Preferly MCP server?
VerifyMCP ran 13 checks on Preferly, 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.