AI Search Kit

com.modernmustardseedPublished by modernmustardseed.comOfficial publisherv1.0.0Updated Oct 25, 2026

Audits AI-crawler access, structured data and llms.txt on a site, and drafts the fixes.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

A remote MCP server that audits a website's readiness for AI answer engines and drafts structured data, llms.txt and consistency fixes.

What you can do
Audit a public page for AI crawler access, reading robots.txt, llms.txt and sitemap and reporting per-crawler controls and structured data findings. Generate schema.org JSON-LD for a local business, choosing the most specific LocalBusiness subtype and valid properties. Write an llms.txt file in the llmstxt.org format, either from supplied content or built from a live site. Compare a business's name, phone and address across up to eight sources to spot inconsistencies. Validate pasted JSON-LD against the schema.org vocabulary and Google's LocalBusiness and Organization rules.
When to use it
Useful when preparing or reviewing a site so AI answer engines can crawl it and understand its content, or when checking and drafting local business markup, llms.txt and directory listings for consistency.
Requirements
Remote streamable HTTP endpoint; no packages, environment variables or headers declared. The audit, llms.txt generation and consistency tools read public web pages, so network access to those sites is needed.
Before you install
Tools read public pages and site files from URLs you supply, so those URLs are sent to the remote service. Generated JSON-LD, llms.txt and consistency reports are drafts to review before publishing; the server does not appear to write to your site.

Installation

In SourceWeft

  1. Open AI Search Kit 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/com.modernmustardseed%2Fai-search-kit/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": {
    "ai-search-kit": {
      "type": "http",
      "url": "https://mcp.modernmustardseed.com/ai-search-kit"
    }
  }
}

Tools

5

audit_ai_readiness

Audit AI search readiness

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.

Parametersurlrequireddetail

generate_local_business_schema

Generate LocalBusiness schema

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.

Parametersurllogonamerequiredemailhoursimagessame_asfounderslatitudemenu_urlserviceslongitude+19 more

generate_llms_txt

Generate llms.txt

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.

Parametersurldetailssummarysectionsmax_pagessite_nameoptional_links

check_entity_consistency

Check entity consistency

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.

Parametersbusinessprofilesrequired

validate_structured_data

Validate structured data

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.

Parametersjson_ldrequired

Version history

1
  1. v1.0.0LatestOct 11, 2026

Score

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

    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.

Other Modernmustardseed integrations