pigfox.ai AI search readiness

ai.pigfoxPublished by pigfox.aiOfficial publisherv1.0.0Updated Nov 8, 2026

Check if a site is ready for AI search: AI crawler access, llms.txt, JSON-LD, scored out of 100.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Audits a website's readiness for AI search — AI crawler access, llms.txt and homepage metadata — and returns a score out of 100 with fixes.

What you can do
  • Check a domain's AI search readiness and get a score out of 100 with its band and suggested fixes
  • Inspect robots.txt access for 15 AI crawlers, including GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and Google-Extended
  • Verify whether the site publishes an llms.txt file
  • Review homepage metadata: title and description lengths, canonical, language, h1 and JSON-LD types
When to use it
Useful when checking whether AI assistants and crawlers are allowed to read a site and can tell what it is, for example before or after SEO/AEO work, or when diagnosing why a page is poorly represented in AI answers.
Requirements
Remote streamable HTTP endpoint at pigfox.ai; no authentication, environment variables or headers declared. Pass a domain such as example.com. Results are cached for 10 minutes and new checks are limited to 6 per minute per client.
Before you install
The score only reflects whether AI tools may read the homepage and identify it; it does not predict rankings or citations. Requests are rate-limited, so repeated checks may return cached results.

Installation

In SourceWeft

  1. Open pigfox.ai AI search readiness 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.pigfox%2Fpigfox-ai/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": {
    "pigfox-ai-ai-search-readiness": {
      "type": "http",
      "url": "https://pigfox.ai/mcp"
    }
  }
}

Tools

1

check_ai_search_readiness

Check AI search readiness

Check whether a website is ready for AI search: per-crawler robots.txt access for GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and 10 more, llms.txt, the homepage's title and description lengths, canonical, language, h1 and JSON-LD types, a score out of 100, its band, and fixes with the points each is worth. Fetches only the homepage, robots.txt, llms.txt and a HEAD of llms-full.txt.

Parameterssiterequired

Version history

1
  1. v1.0.0LatestNov 8, 2026

Score

72% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.