Site Check MCP server

• check_ai_search_readinessFree

  Check whether AI assistants and answer engines can read and quote a public website: which AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended and others) its robots.txt allows or blocks, whether it publishes llms.txt, which structured data types it declares, how its title and description read, and the search and AI checks with fixes. Shares the 24 hour cache with scan_website.

• explain_checkFree

  Explain one Site Check check by its id (as returned by scan_website): what it measures, the pass and fail thresholds, why it matters, how to fix it, and the typical effort. Static reference, no network access.

• scan_websitewrite actionFree

  Run a measured health check of a public website homepage: speed (server response, page weight, scripts, image formats), security (HTTPS, certificate expiry, security headers), domain registration expiry, email authentication (MX, SPF, DMARC), search basics (title, description, headings, indexability, sitemap), AI search readiness (structured data, AI crawler rules, llms.txt) and contact paths (tap to call, forms, analytics). Every result is measured, not judged by a model, and each warn or fail comes with a fix and an effort level. Returns a 0 to 100 website score, the top fixes, and how the page appears in a search result. Results are cached for 24 hours. Use detail "full" to include passing checks.

• score_local_presenceFree

  Score a local business on three pillars, website (45 percent), Google reviews (30 percent) and Google Business Profile (25 percent), and return an overall 0 to 100 score, a letter grade, each pillar with its verdict, and the top fixes. The website pillar comes from a live scan when a website is given. Review and profile facts (rating, review count, phone, address, hours) are supplied by the caller from the user or from a public listing; this tool does not look them up. A pillar with no facts is marked unknown and left out of the overall score rather than scored as zero.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 358ms20/20
• Tool poisoning4 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

65/100

higher than 20% of 918 Security servers

Tools

4

the typical Security server has 6

Tools that change things

25%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Security server answers 100%

Response time

479 ms

faster than 24% of 550 Security servers

Site Check: common questions

Is Site Check MCP server safe?

With care: it is graded C, so read the findings first (65/100). Read the Site Check safety report

How do I install Site Check?

It runs remotely at mcp.modernmustardseed.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Site Check need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Site Check maintained?

The latest release is v1.0.0.

Is Site Check up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Site Check?

Servers from other publishers that do the same job: Autopilot Jobhunt MCP server, DNS Doctor MCP server and prodlint MCP server.

How does Site Check compare with other Security MCP servers?

safety score 65/100 (higher than 20% of 918 Security servers); tools 4 (the typical Security server has 6); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.