Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AI Search Kit

REMOTE · MCP.MODERNMUSTARDSEED.COM

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

+4 this week 75 Trust /100

Last scanned (1 hour ago)

Scores higher than 69% of remote servers

Reachable. Last reached 23 Oct 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1569 tokens (~313/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Oct 2026 · Probed https://mcp.modernmustardseed.com/ai-search-kit

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.modernmustardseed.com CN=YR2,O=Let's Encrypt,C=US 11 Oct 2026 9 Jan 2027 RSA 2048 SHA256-RSA 5037aab1b1b95f22d0713db17fad3a7354f
SANs: mcp.modernmustardseed.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.modernmustardseed.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
modernmustardseed.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.modernmustardseed.com/ai-search-kit Verified 200
http (plaintext) http://mcp.modernmustardseed.com/ai-search-kit HTTPS enforced 308 https://mcp.modernmustardseed.com/ai-search-kit
MCP tools · 5 exposed · ~1,470 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
audit_ai_readiness ~262

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.

NameTypeReqDescription
detailstring–"summary" (default) lists only findings that warn, fail or inform; "full" includes passing findings with their sources.
urlstringyesThe page to audit, such as example.com or https://example.com/locations/denver. Public http and https only.

No output schema declared.

No examples provided.

check_entity_consistency ~191

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.

NameTypeReqDescription
businessobject–The canonical name, phone and address every source should match.
profilesarrayyes–

No output schema declared.

No examples provided.

generate_llms_txt ~270

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.

NameTypeReqDescription
detailsstring–Optional markdown notes between the summary and the link sections. Headings are not allowed there.
max_pagesinteger–How many pages to read from the site, 1 to 30. Default 20.
optional_linksarray–Secondary links for the Optional section.
sectionsarray–H2 file lists, each with links.
site_namestring–The H1. Required when url is not given.
summarystring–One or two sentences for the blockquote.
urlstring–A public site to read, such as example.com.

No output schema declared.

No examples provided.

generate_local_business_schema ~625

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.

NameTypeReqDescription
accepts_reservationsboolean–Food businesses only.
address_countrystring–Two-letter ISO country code, such as "US".
address_localitystring–City or town.
address_regionstring–State, province or region, such as "MT".
area_servedarray–Places served: plain names, or objects with a type (City, State, AdministrativeArea, Country, Place) and an optional Wikidata or Wikipedia URL in same_as.
business_typestring–Plain words for what the business is, such as "plumber", "dental office" or "coffee shop".
currencies_acceptedarray–ISO 4217 codes such as USD.
descriptionstring––
emailstring––
foundersarray––
founding_datestring–YYYY-MM-DD.
hide_street_addressboolean–True for a service-area business that does not serve customers at its address.
hoursarray–Regular opening hours. Days not listed read as closed.
imagesarray––
latitudenumber––
logostring–Logo image URL.
longitudenumber––
menu_urlstring–Food businesses only.
namestringyesBusiness name as shown on the storefront, website and Google profile.
open_24_7boolean–True when the business is open 24 hours every day. Overrides hours.
payment_acceptedarray––
postal_codestring––
price_rangestring–Such as "$$" or "$100-$300". Under 100 characters.
same_asarray–Official profile URLs that identify the business: Google Business Profile, Facebook, LinkedIn, Yelp, Wikidata.
schema_type––An exact schema.org LocalBusiness subtype, or up to three, such as "Plumber". Overrides business_type.
seasonal_closuresarray–Closed periods, dates as YYYY-MM-DD.
serves_cuisinearray–Food businesses only.
servicesarray–Services offered, written as Offer items.
street_addressstring––
telephonestring–Primary customer phone number. North American numbers are written as +1-AAA-BBB-CCCC.
urlstring–The business website or location page.

No output schema declared.

No examples provided.

validate_structured_data ~122

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.

NameTypeReqDescription
json_ldstringyesJSON-LD text. Script tags are stripped; several script blocks are each validated.

No output schema declared.

No examples provided.

Install

How do I install the AI Search Kit MCP server?

AI Search Kit is a hosted endpoint at https://mcp.modernmustardseed.com/ai-search-kit, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.modernmustardseed.com

# add to Claude Code
claude mcp add --transport http com-modernmustardseed-ai-search-kit 'https://mcp.modernmustardseed.com/ai-search-kit'
Common questions

What is the AI Search Kit MCP server?

AI Search Kit is an MCP server listed in the public MCP registry as com.modernmustardseed/ai-search-kit. Audits AI-crawler access, structured data and llms.txt on a site, and drafts the fixes. This page covers its hosted endpoint (https://mcp.modernmustardseed.com/ai-search-kit).

Is the AI Search Kit MCP server safe to use?

AI Search Kit scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AI Search Kit MCP server expose?

AI Search Kit exposes 5 tools: audit_ai_readiness, generate_local_business_schema, generate_llms_txt, check_entity_consistency, validate_structured_data. Their descriptions and schemas cost roughly 1,470 tokens of context every time the server is loaded.

Does the AI Search Kit MCP server require authentication?

No. We connected to AI Search Kit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AI Search Kit MCP server still maintained?

AI Search Kit is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.