SyteCheck MCP Server
Related Servers
Alternatives to SyteCheck MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to crawl and audit websites for SEO and technical health, checking on-page elements, links, robots.txt, sitemaps, and duplicate metadata, then returning scores and prioritized fixes.414 npmMIT
- AlicenseNot gradedqualityAmaintenanceExposes website auditing, finding retrieval, and safe fix application as MCP tools so AI agents can diagnose and remediate SEO, accessibility, and technical web issues.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables running comprehensive SEO audits on websites, checking meta tags, sitemaps, robots.txt, broken links, headings, duplicate titles, and keyword density through MCP tools.13 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to perform bounded website Quick Audits via MCP tools, covering crawlability, indexability, and metadata.1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to run fresh audits of any public web page on mobile or desktop, returning category scores, lab metrics, and prioritized findings for performance, accessibility, best practices, and SEO. Each call performs a new uncached audit, so users can compare results within a conversation.11MIT

io.github.spalofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents and CI systems to run deterministic website QA audits over MCP, with every finding backed by evidence and every result hashed and signed. It checks HTTP, TLS, security headers, SEO, links, accessibility, and robots.txt, with configurable pass/fail verdicts.MIT
TDQS
Scored across 6 tools
Each tool targets a distinct object and action: run_scan creates, get_scan_report reads one scan's findings, get_scan_trends reads history per URL, list_scans indexes scans, list_categories describes analyzers, get_account_usage reports quota. The report/trends/list distinction is spelled out in the descriptions, so misselection is unlikely.
All six names follow a strict verb_noun snake_case pattern (get_*, list_*, run_*). Verbs are used consistently: get_ for single-resource fetches, list_ for collections, run_ for the mutating action.
Six tools covering quota, categories, submission, retrieval, listing, and trends is well-matched to a single-purpose scanning service with no redundant entries. Nothing feels padded or missing at the count level.
The core lifecycle (check quota/categories, submit scan, collect report, review trends, list history) is fully covered. Minor gaps exist, such as no way to cancel or delete a scan, but these are workable and scans are likely immutable.