Preferly

ai.preferlyPublished by preferly.aiOfficial publisherv1.0.1Updated Nov 14, 2026

Free AI visibility checks for any website: AI crawler access, llms.txt, schema, business info.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Free hosted checks that tell an assistant whether AI crawlers and AI tools can reach and read a given website.

What you can do
  • Check AI crawler access: read robots.txt and report which of 13 AI crawlers are allowed or blocked, and whether the homepage loads for them
  • Check llms.txt: report whether /llms.txt exists, its size and title, and format problems with line numbers
  • Check structured data: report the business type and which schema.org fields are present, missing or look off
  • Check readable business info: report whether name, phone, email, address, hours and prices appear as text without scripts
  • Generate robots.txt lines that let AI search crawlers in and keep training crawlers out, with optional private paths
  • Run a quick visibility check that asks 3 AI models 3 typical customer questions about the business
When to use it
Useful when someone wants to know why a site may not show up in AI answers, is auditing AI crawler rules, llms.txt or business schema, or needs ready-made robots.txt lines for AI crawlers.
Requirements
A remote streamable HTTP endpoint; nothing to install. No sign-up, API key or authentication. Each call takes one public website. Usage is rate limited per caller and per website.
Before you install
Read-only and fetches only public pages, but each check is recorded along with the optional client name passed in the URL. The quick visibility check sends the site's public content to AI models. The full multi-model report is a separate paid product.

Installation

In SourceWeft

  1. Open Preferly in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.preferly%2Fpreferly/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "preferly": {
      "type": "http",
      "url": "https://www.preferly.ai/mcp"
    }
  }
}

README

[Preferly logo]

Preferly MCP server

Free AI visibility checks for any website, inside Claude, ChatGPT, Cursor, VS Code and any other AI tool that speaks the Model Context Protocol (MCP). Ask your assistant whether AI crawlers can reach a site, whether its llms.txt and business schema are right, and whether AI can read its hours and prices, and it runs Preferly's checks for you.

https://www.preferly.ai/mcp

Streamable HTTP · No sign-up · No API key · Read-only

This is a hosted (remote) server, so there is nothing to install or run. This repository holds the documentation and ready-made configs. The server itself runs at preferly.ai.

[Add to Cursor] [Install in VS Code] [Install in VS Code Insiders]

Tools

Every tool is read-only and works on one public website per call. None of them changes anything on the site.

ToolInputWhat it does
check_ai_crawler_accesswebsiteWhether the site's robots.txt lets 10+ AI crawlers in (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended and more) and which rule decides each one; whether the homepage loads for them or shows a bot check; whether it has /llms.txt; its structured data types.
generate_ai_robots_txtallow_search (default true), allow_training (default false), optional disallow_pathsrobots.txt lines that let AI search and assistant crawlers in and keep training crawlers out, or any mix. Fetches nothing.
check_llms_txtwebsiteWhether the site publishes /llms.txt, its size and title, and what doesn't follow the llmstxt.org format, with line numbers.
check_business_schemawebsiteThe business described in the homepage's structured data (JSON-LD): its type, and which fields are present, missing or look off.
check_business_infowebsiteWhether the site's name, phone, email, address, hours and prices are readable as text without running scripts.
quick_ai_visibility_checkwebsiteAsks 3 AI models 3 typical customer questions about the business, from its public website, and reports whether each named it and where one contradicts the website.

The live list is always in the server card and the server's tools/list.

Set up

Most clients only need the URL. Adding ?client=<your tool> helps us count which tools people use; it's optional.

Any client, one command

bash
npx add-mcp https://www.preferly.ai/mcp

add-mcp finds the MCP clients on your computer and adds Preferly to them.

Claude Code

bash
claude mcp add --transport http preferly "https://www.preferly.ai/mcp?client=claude"

Claude (claude.ai and Claude Desktop)

Open Settings → Connectors → Add custom connector.

  • Name: Preferly
  • URL: https://www.preferly.ai/mcp?client=claude

Leave authentication empty and save. Then turn Preferly on from the tools menu in a chat. Custom connectors are available on Claude's paid plans.

ChatGPT (developer mode)

In ChatGPT on the web, open Settings → Apps → Advanced settings, turn on Developer mode, then choose Create app.

  • Name: Preferly
  • MCP server URL: https://www.preferly.ai/mcp
  • Authentication: No authentication

Whether developer mode is available depends on your plan and workspace settings. A listed Preferly app for ChatGPT is in review.

Cursor

Use the Add to Cursor button above, or add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

json
{  "mcpServers": {    "preferly": { "url": "https://www.preferly.ai/mcp?client=cursor" }  }}

VS Code (GitHub Copilot)

Use the Install in VS Code button above. You can also run MCP: Add Server → HTTP and paste https://www.preferly.ai/mcp?client=vscode, or add this to .vscode/mcp.json:

json
{  "servers": {    "preferly": { "type": "http", "url": "https://www.preferly.ai/mcp?client=vscode" }  }}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

json
{  "mcpServers": {    "preferly": { "serverUrl": "https://www.preferly.ai/mcp?client=windsurf" }  }}

Cline

Open the MCP Servers panel → Remote Servers, name it preferly and paste https://www.preferly.ai/mcp?client=cline. You can also add this to cline_mcp_settings.json:

json
{  "mcpServers": {    "preferly": { "type": "streamableHttp", "url": "https://www.preferly.ai/mcp?client=cline" }  }}

To let Cline set it up for you, point it at llms-install.md.

Codex

bash
codex mcp add preferly --url "https://www.preferly.ai/mcp?client=codex"

Gemini CLI

Add to ~/.gemini/settings.json:

json
{  "mcpServers": {    "preferly": { "httpUrl": "https://www.preferly.ai/mcp?client=gemini" }  }}

Goose

Run goose configure → Add Extension → Remote Extension (Streamable HTTP), name it preferly and use https://www.preferly.ai/mcp?client=goose.

Zed

Add to your Zed settings.json:

json
{  "context_servers": {    "preferly": { "url": "https://www.preferly.ai/mcp?client=zed" }  }}

If your Zed version only runs local servers, use the bridge instead: "command": "npx", "args": ["-y", "mcp-remote", "https://www.preferly.ai/mcp?client=zed"].

Hermes Agent

bash
hermes plugins install preferly-ai/preferly-hermes --no-enablehermes plugins enable preferly

The plugin (preferly-ai/preferly-hermes) adds the server plus a skill that tells Hermes when to use each tool.

Other clients

Point the client at https://www.preferly.ai/mcp (streamable HTTP, no auth). If it only runs local (stdio) servers, use mcp-remote:

json
{  "mcpServers": {    "preferly": { "command": "npx", "args": ["-y", "mcp-remote", "https://www.preferly.ai/mcp"] }  }}

A generic config is in mcp.json.

Try asking

  • "Can AI crawlers read example.com?"
  • "Does my robots.txt block GPTBot or ClaudeBot?"
  • "Write robots.txt lines that let AI search crawlers in, keep training crawlers out, and keep /admin private."
  • "Does example.com have a valid llms.txt?"
  • "Is the business schema on example.com complete?"
  • "Can AI read the phone number, hours and prices on example.com without running scripts?"
  • "What do AI assistants say about the business at example.com?"

Limits, privacy and safety

  • Free, no sign-up and no key. Each caller gets 10 calls an hour and 30 website checks a day. Each website gets at most 20 fresh checks a day across all callers. A check for the same website in the last 10 minutes may be reused.
  • The website checks fetch only public pages: robots.txt, the homepage, /llms.txt, and at most 2 contact, booking or pricing pages that robots.txt allows. They identify themselves as PreferlyBot. They never log in, submit forms or change anything.
  • generate_ai_robots_txt fetches nothing.
  • Only quick_ai_visibility_check calls AI models, and it uses only what the website says publicly.
  • Preferly records each check and the client name you pass in ?client= to apply these limits and count usage. See the privacy policy.

What these checks don't do

They check whether AI can reach and read a website, not what AI assistants actually say about a business. For that, Preferly's full report asks 10 leading AI models about your business, quotes every place they contradict your website, and gives you the fixes ready to paste, for $99 once. See an example report.

Links

License

The documentation and configs in this repository are MIT licensed (see LICENSE). The hosted server is operated by Preferly.

Source: README.md at commit afcea5c

Tools

6

check_ai_crawler_access

Check AI crawler access

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 13 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.

Parameterswebsiterequired

check_llms_txt

Check llms.txt

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.

Parameterswebsiterequired

check_business_schema

Check business structured data

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.

Parameterswebsiterequired

check_business_info

Check readable business info

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.

Parameterswebsiterequired

generate_ai_robots_txt

Generate AI robots.txt lines

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.

Parametersallow_searchallow_trainingdisallow_paths

quick_ai_visibility_check

Quick AI visibility check

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.

Parameterscitywebsiterequiredbusiness_name

Version history

1
  1. v1.0.1LatestNov 14, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts