AI Search Kit

{
  "mcpServers": {
    "com.modernmustardseed/ai-search-kit": {
      "url": "https://mcp.modernmustardseed.com/ai-search-kit"
    }
  }
}

Indexed tools

Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.

5 shown · authentication unknown

• Audit AI search readiness

  audit_ai_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.

  Schema valid · SHA-256 008ea758a57a…

  View input schema

  {
    "type": "object",
    "properties": {
      "url": {
        "type": "string",
        "minLength": 3,
        "maxLength": 2048,
        "description": "The page to audit, such as example.com or https://example.com/locations/denver. Public http and https only."
      },
      "detail": {
        "default": "summary",
        "description": "\"summary\" (default) lists only findings that warn, fail or inform; \"full\" includes passing findings with their sources.",
        "type": "string",
        "enum": [
          "summary",
          "full"
        ]
      }
    },
    "required": [
      "url"
    ],
    "$schema": "https://json-schema.org/draft/2020-12/schema"
  }

• 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.