MCP App Store
by KeenEthics
Sales-And-Marketing
AI Search Kit by Modern Mustard Seed icon

AI Search Kit by Modern Mustard Seed

by Modern Mustard Seed

Overview

AI Search Kit helps any business become easy for AI answer engines to find, read and cite. audit_ai_readiness reads one public page plus its site's robots.txt, llms.txt and sitemap. It reports, for 12 AI crawlers and control tokens from OpenAI, Anthropic, Perplexity, Google and Apple, whether robots.txt lets each one read the page under RFC 9309 matching. It also reports noindex and nosnippet directives, JSON-LD validity against the schema.org vocabulary and Google's LocalBusiness rules, whether the name, phone and address in the markup appear on the visible page, llms.txt format, the canonical tag and the sitemap. generate_local_business_schema turns business facts into JSON-LD using the most specific of 130 LocalBusiness subtypes, with hours and phone in Google's documented formats, and validates its own output. generate_llms_txt writes an llms.txt in the llmstxt.org format from your facts or from a live site, honoring its robots.txt. check_entity_consistency compares name, phone and address across up to 8 profiles and lists the exact fixes. validate_structured_data checks pasted JSON-LD. Every finding cites the public spec or vendor document behind it, with the date it was read. All tools are read-only, need no account, and call no AI model.

Tools

audit_ai_readiness

Claude
Audit one public web page for what AI answer engines and their crawlers rely on. Reads the page plus its site's robots.txt, llms.txt and sitemap, then reports: for each AI crawler and control token (OAI-SearchBot, ChatGPT-User, GPTBot, Claude-SearchBot, Claude-User, ClaudeBot, PerplexityBot, Perplexity-User, Googlebot, Google-Extended, Applebot, Applebot-Extended) whether robots.txt allows it on this page under RFC 9309 matching; noindex and nosnippet directives; JSON-LD validity against the schema.org vocabulary and Google's LocalBusiness rules; whether the name, phone and address in the markup also appear on the visible page; llms.txt format; canonical tag; and sitemap. Every finding cites the public spec or vendor document behind it, with the date it was read. Results are cached for 10 minutes.

check_entity_consistency

Claude
Compare a business's name, phone, street, city, region and postal code across up to 8 sources, such as its website, Google Business Profile, Facebook page and directory listings. For each source give a url to read (JSON-LD first, then tap-to-call links and page text) and/or the facts shown on it; supplied facts win, and are needed for sites that block automated readers. Formats are normalized ("123 North Main Street, Suite 4" matches "123 N Main St Ste 4", "(406) 555-0100" matches "+1 406-555-0100"), then each field is reported as consistent, variant or mismatch, with the exact fixes. Give business to compare against a canonical record instead of the majority.

generate_llms_txt

Claude
Write an llms.txt file in the llmstxt.org format: an H1 with the site name, a blockquote summary, optional details, H2 sections of "- [title](url): note" links, and an Optional section for secondary pages. Give url to build it from the live site (home page, sitemap, and up to 30 pages' own titles and meta descriptions, honoring the site's robots.txt and skipping noindex pages), or give site_name and sections to build it from your own facts; supplied fields override what is read from the site. The result is checked against the format before it is returned. Nothing is published.

generate_local_business_schema

Claude
Turn a local business's facts into schema.org JSON-LD. Chooses the most specific LocalBusiness subtype from business_type (for example "roofing company" becomes RoofingContractor) or takes schema_type as given, writes only properties schema.org defines for that type, formats hours, phone and 24 hour or closed days the way Google documents, then validates the output against the schema.org vocabulary. Returns the JSON-LD, a ready-to-paste script tag, the type chosen with alternatives, and cited notes on anything left out. No network access; nothing is published.

validate_structured_data

Claude
Validate pasted JSON-LD against the schema.org vocabulary (every type, property, domain, range and enumeration value) and Google's documented rules for LocalBusiness and Organization markup: required name and address, recommended properties, hh:mm:ss hours, 5 decimal coordinates, priceRange length, self-serving reviews, sameAs. Accepts one block, several blocks, or the script tags around them. Each issue cites its source. No network access.