Skip to content

Preferly MCP server

ai.preferly/preferlypreferly.aistreamable-httpv1.0.1Scanned

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

6 tools: 6 change things.

Tools: 0 delete, 0 irreversible, 6 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Preferly MCP server can do

The Preferly MCP server is published by preferly.ai, a domain the MCP Registry verified. It has 6 tools. It can create or change data (6 tools: check_ai_crawler_access, check_llms_txt, check_business_schema, check_business_info and 2 more), but cannot delete data. None of its tools only reads.

5 tools bring in text other people can write (check_ai_crawler_access, check_llms_txt, check_business_schema and 2 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 6Claude Code: ask
  • check_ai_crawler_accessUse this when the user wants to know whether AI crawlers and AI tools can access a specific website.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: true
  • check_business_infoUse this when the user asks whether AI tools can read a business's details from its website.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: true
  • check_business_schemaUse this when the user asks whether a website's structured data (schema.org JSON-LD) describes the business correctly.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: true
  • check_llms_txtUse this when the user asks whether a website has an llms.txt file or whether it's set up correctly.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: true
  • generate_ai_robots_txtUse this when the user wants robots.txt lines that control which AI crawlers may read their website.1 finding

    Why it is in this group

    • The name "generate_ai_robots_txt" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "generate_ai_robots_txt" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_ai_robots_txt" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • quick_ai_visibility_checkUse this when the user asks what AI assistants say about a specific business, or whether AI tools mention or recommend it.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.preferly.ai/mcp: tools/list returned 6 tools to an anonymous client, including check_ai_crawler_access (write), check_llms_txt (write), check_business_schema (write), check_business_info (write), generate_ai_robots_txt (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "generate_ai_robots_txt" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_ai_robots_txt" says "generate": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http preferly https://www.preferly.ai/mcp
claude mcp add --transport http preferly https://www.preferly.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__preferly__check_ai_crawler_access",
      "mcp__preferly__check_llms_txt",
      "mcp__preferly__check_business_schema",
      "mcp__preferly__check_business_info",
      "mcp__preferly__generate_ai_robots_txt",
      "mcp__preferly__quick_ai_visibility_check"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as preferly. Review it before you use it.

Capability tags behind 5 rules
  • mcp__preferly__check_ai_crawler_access untrusted-input
  • mcp__preferly__check_llms_txt untrusted-input
  • mcp__preferly__check_business_schema untrusted-input
  • mcp__preferly__check_business_info untrusted-input
  • mcp__preferly__quick_ai_visibility_check untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.preferly/preferly/verify?hash=67a5d3658e843302b18b015b3ab810f4956f0640fe4330047db274d53ab75855" | jq -e '.changed == false'

Pinned hash 67a5d3658e84, from Nov 14, 2026, 16:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.preferly/preferly/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.preferly/preferly
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.preferly/preferly.svg)](https://radar.anlyon.com/servers/ai.preferly/preferly)

Source: MCP Registry · repository. Synced Nov 14, 2026, 16:17 UTC.

Preferly MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Preferly MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Preferly MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Preferly MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Preferly MCP server have?

6 tools: 6 write. check_ai_crawler_access, check_llms_txt, check_business_schema, check_business_info, generate_ai_robots_txt and quick_ai_visibility_check.

Does the Preferly MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Preferly MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Preferly MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.