AI Readiness

io.github.epistemedeusPublished by GitHub account epistemedeusv1.1.3Updated Oct 24, 2026

Check if a website is visible to AI search (ChatGPT, Perplexity, Claude) and get per-gap fixes.

The publisher's own server: SameDayDesk agent tools

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Checks whether a website is crawlable and well-structured for AI search engines, returning a score, grade, and per-gap fixes.

What you can do
Exposes two tools: check_ai_readiness(url) returns a 0-100 score, letter grade, and a specific fix for each failing check, and generate_ai_readiness_fixes(url) produces starter Organization and FAQPage JSON-LD plus an AI-crawler-friendly robots.txt. Checks cover AI crawler access in robots.txt, JSON-LD structured data, title and meta description, Open Graph tags, XML sitemap, and llms.txt. It runs locally over stdio and can also be used as a CLI or in CI.
When to use it
Useful when you want an assistant to audit a site's technical eligibility for AI search citations, or to draft structured data and robots.txt fixes inline. Suited to site owners, SEO and marketing work, and pre-deploy checks.
Requirements
Node.js 18 or newer; the server runs as a local stdio process, typically launched with npx. No account, signup, API key, or environment variable is declared. Network access is needed to fetch the target site.
Before you install
The server fetches the URL you give it, so only point it at sites you are authorized to check. The generated robots.txt and JSON-LD are starter files that would change how crawlers treat a site if applied; review before deploying. The README also promotes paid products and services, which are separate from the free tool.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ai-readiness

Is your website visible to AI search? A tiny, dependency-free CLI that checks whether ChatGPT, Perplexity, Claude, and Google AI can crawl and understand your site, and tells you exactly what to fix.

bash
npx github:epistemedeus/ai-readiness yoursite.com

No install, no signup, no dependencies. Node 18+.

Prefer a browser? Run the same check (no install) at samedaydesk.com/tools/ai-readiness.


📦 Want the fixes done for you? AI Search Readiness Kit: $9

The checker tells you what to fix. This kit gives you everything to fix it, ready to paste:

  • Copy-paste robots.txt (welcomes every AI crawler), Organization + WebSite + FAQPage JSON-LD, title/meta/Open Graph templates, and an XML sitemap
  • The 7-fix priority checklist in order of impact
  • The full benchmark behind the dataset below
  • Delivered instantly after checkout, no signup

→ Get the AI Search Readiness Kit ($9) · Prefer a done-for-you audit of your site? See samedaydesk.com.

Dataset: 136 companies scored for AI-search readiness (June 2026)

We ran this checker against the homepages of 136 well-known companies across 7 industries and published the full results. Open data, free to use with attribution.

Average score by industry (lower = harder for AI search to read):

IndustryAvg scoren
Marketing agencies9224
SaaS8824
Dev tools8617
E-commerce8519
AI startups8325
Fintech7416
Healthtech6311

Notable findings: Healthtech is the least AI-search-ready industry (avg 63). Klarna scored an F (38); GitHub, Chime, Ramp, Gusto, Ro, Hims and Zocdoc each scored a D. Even some AI companies struggle. Perplexity scored a C and LlamaIndex a D. Most gaps are the same and entirely fixable: JavaScript-only homepages, missing JSON-LD structured data, and no sitemap.

Per-industry write-ups: SaaS · e-commerce · marketing agencies · AI startups · healthtech.

Why this matters

AI search is becoming how people find things, and AI answers are pulled from a small set of pages that are crawlable and well-structured. If GPTBot is blocked in your robots.txt, or your pages have no structured data, you can be invisible in AI answers no matter how good your site looks to humans. This tool checks the technical fundamentals that decide whether you're even eligible to be cited.

What it checks

CheckWhy it matters
AI crawler accessWhether GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, Bingbot are allowed in robots.txt. Blocked = invisible.
Structured data (JSON-LD)AI engines use JSON-LD (Organization, FAQPage, Article) to classify and quote your content.
Title & meta descriptionPresent and well-sized, so engines have a clean summary to work with.
Open Graph tagsRicher machine-readable context and clean link previews.
XML sitemapHelps engines discover your pages; submit it in Bing Webmaster Tools (ChatGPT Search reads the Bing index).
llms.txtFlagged as cheap hygiene only. Honest note: it has no proven effect on AI citations yet, so don't let anyone sell it to you as a ranking boost.

You get a 0-100 score, a letter grade, and a concrete fix for every failing check.

Example

$ npx github:epistemedeus/ai-readiness example.com
AI Readiness  https://example.com/Score 72/100  Grade B
  PASS  AI crawler access  No AI crawler blocked.  FAIL  Structured data (JSON-LD)  None found.        fix: Add Organization + FAQPage + Article JSON-LD.  PASS  Title & meta description  title 41 chars, description 132 chars  WARN  Open Graph tags  2 og: tags        fix: Add og:title, og:description, og:image, og:url.  PASS  XML sitemap  found  WARN  llms.txt  none (minor: no proven citation effect)

JSON output for scripting: npx github:epistemedeus/ai-readiness yoursite.com --json

Use as an MCP server

Add the checker to any Model Context Protocol client (Claude Desktop, Cursor, Cline, etc.) so you can ask your AI assistant "is my site visible to AI search?" and get a scored report inline. Dependency-free, runs over stdio.

json
{  "mcpServers": {    "ai-readiness": {      "command": "npx",      "args": ["-y", "github:epistemedeus/ai-readiness", "mcp"]    }  }}

It exposes two tools:

  • check_ai_readiness(url): returns the score, grade, and a specific fix for each gap.
  • generate_ai_readiness_fixes(url): generates starter Organization + FAQPage JSON-LD (pre-filled from the site) and an AI-crawler-friendly robots.txt.

This standalone package is the two-tool local MCP server. Use the npx stdio config above (npx -y github:epistemedeus/ai-readiness mcp, or node mcp.js). http.js is a minimal stateless custom JSON-RPC-over-HTTP POST adapter (POST /mcp); it is not MCP Streamable HTTP, not a production remote MCP transport, and ordinary Streamable HTTP clients cannot use it as-is. There is no hosted remote MCP URL for this package.

Use in CI (GitHub Action)

Fail-fast on AI-search regressions by checking a URL on every deploy:

yaml
- uses: epistemedeus/ai-readiness@v1  with:    url: https://yoursite.com

The deep version

This CLI checks the technical basics. The questions it can't answer from your markup: do ChatGPT, Perplexity, and Google AI actually cite you for the queries your buyers type? How do you compare to named competitors? What's the highest-ROI fix first?

That's the AI-Search Visibility Audit from SameDayDesk: real citation testing across engines, a competitor benchmark, and a prioritized fix list as a PDF and web report, delivered same day. → samedaydesk.com

Need a custom MCP server?

Like how this one is built: dependency-free, stdio plus a custom JSON-RPC-over-HTTP POST adapter, published to the MCP registry, two focused tools? We build MCP servers for your API or product the same way. (Curious how? Read the guide: How to build a dependency-free MCP server.)

Custom MCP Server: $349, delivered fast. You get a working server (stdio + optional hosted remote), wired to your API, with the registry/manifest setup done. → get one built (or buy directly).

Guides

Free, in-depth guides on getting your site read and cited by AI search:

License

MIT © SameDayDesk

Source: README.md at commit 243749a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.3LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Samedaydesk integrations