MCP Web Validator
Related Servers
Alternatives to MCP Web Validator
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI coding assistants to validate HTML/CSS markup using W3C APIs, perform technical SEO audits, check broken links, and validate JSON-LD schemas directly in local workspaces.88,300 npm7MIT
- FlicenseNot gradedqualityCmaintenanceEnables natural language technical and JavaScript SEO audits, including headless rendering, hydration gap analysis, schema validation, AEO checks, and semantic cannibalization detection.1-
- AlicenseAqualityBmaintenanceLets developers and MCP agents run deterministic local HTML audits, turning inline HTML into structured findings for missing labels, unnamed buttons, skipped headings, ambiguous links, duplicate IDs, and missing landmarks. It also exposes a rule list and returns stable, actionable reports without external API keys.2MIT
- FlicenseNot gradedqualityDmaintenanceEnables auditing of websites for performance, SEO, accessibility, security, and mobile readiness, with tools to validate URLs, run page audits, save results, and retrieve reports.1-
- AlicenseAqualityDmaintenanceEnables SEO auditing and site analysis by crawling websites, identifying issues, and generating reports like sitemaps and markdown exports.52 npm4MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to perform full SEO audits on unpublished HTML, Markdown, or Word documents, including keyword analysis, meta tag suggestions, readability scoring, and heading structure validation.12 npmMIT
TDQS
Scored across 2 tools
The two tools target clearly different validation areas: SEO HTML metadata versus JSON-LD schema markup. There is no overlap in purpose, so an agent can easily choose between them.
Both tool names follow the same namespace.action convention: seo.metadata and schema.markup. The pattern is predictable and consistent across the set.
Two tools is borderline thin for a server called 'MCP Web Validator,' which implies broader validation coverage. The count is reasonable only if the server is intentionally limited to SEO/schema checks.
For a web validator, the surface has significant gaps: it lacks checks for links, accessibility, performance, canonical tags, Open Graph, robots directives, and deeper schema validation. It covers a narrow slice of SEO/schema markup inspection rather than a complete web validation lifecycle.