QualityKit
Related Servers
Alternatives to QualityKit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to crawl live websites, audit AEO readiness, generate Schema.org @graph JSON-LD, llms.txt, ai.txt, and robots.txt, inject structured data into HTML, validate optimizations, and retrieve framework-specific code snippets.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to audit URLs, static build output, raw HTML, and whole sites for SEO issues, returning actionable findings with rule IDs, severities, fixes, selectors, and evidence, plus optional JavaScript rendering and Lighthouse performance checks.5,518 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to audit a site's technical SEO and AI-search readiness — including localhost dev servers — and retrieve rule explanations, fix templates, and generated llms.txt files so the assistant can edit the repo to resolve what it finds.6 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to audit public or localhost pages, gather structured SEO evidence, and retrieve compact reports, finding details, and next actions for triage.MIT
- AlicenseAqualityBmaintenanceEnables a coding agent to audit a deployed Next.js or Vercel site for SEO and indexing problems such as redirects, robots.txt, sitemaps, canonicals and noindex, returning the CLI's findings as JSON. It also explains issue codes and lists available checks, all read-only over stdio.3107 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to audit a web page in one call — title, meta description, canonical, robots, Open Graph, headings, JSON-LD, security headers and page delivery — returning each finding with its evidence and a ready patch to apply. It also compares a deploy preview against production to surface only regressions, keeps audited pages in tabs with history and daily watches, and runs Lighthouse lab tests via PageSpeed Insights.1MIT No Attribution
TDQS
Scored across 23 tools
Several tools are explicitly redundant: seo.audit is self-described as an 'alias of the audit engine' with 'Prefer qualitykit.audit', and seo.plan_changes, codebase.analyze, blog.scaffold, links.plan, content.brief, and schema.plan all overlap with qualitykit.plan/fix. The 'prefer X' notes help an attentive agent, but six planning-adjacent tools and three audit-adjacent tools create real misselection risk.
A namespace.action pattern (qualitykit.*, seo.*, opportunities.*, visibility.*) is mostly followed, which keeps names readable and grouped. However verb forms vary widely within that pattern — bare verbs/nouns (plan, grow, fix, verify, status) mixed with verb_noun (get_site_profile, mark_applied, plan_changes) — so the surface is not fully predictable.
23 tools is heavy for this domain, and the count is inflated by deprecated/secondary aliases (seo.audit, seo.plan_changes, codebase.analyze) plus three narrow specialized planners that the primary plan tool already covers. Trimming the aliases would leave a tighter, more defensible set.
The audit → plan → fix → verify → monitor → visibility loop is present, along with Site Profile get/refresh/update and an opportunities backlog. But update_site_profile references approveMaterial and approvePending tools that are not in this surface, leaving a dead end, and there is no project/workspace management or explicit deploy step.